3👍
A look at the source code reveals that Django first checks to see if there are any entries that already exist in the database, and then only adds the new ones. It doesn’t return any information to the caller, though.
It’s not clear if you actually need to detect duplicates, or if you just want to make sure that they’re not being added to the database? If it’s the latter then everything’s fine. If it’s the former, there’s no way around hitting the database. If you’re really concerned about performance you could always perform the check and update the through table yourself (i.e. re-implement add()
).
Source:stackexchange.com