loaddata primary key collision behavior

Data Restoration Constraints

Django's dumpdata and loaddata utilities provide a mechanism for serializing and deserializing ORM model instances. While loaddata can populate a database from these fixtures, it requires the underlying schema to be present via migrations before execution.

Primary Key Handling

A known constraint occurs when the fixture contains primary keys that already exist in the target database. The current implementation triggers an IntegrityError, causing the entire load process to abort. There is no native configuration to define how the system should handle these collisions, such as skipping existing records or updating them with the fixture's values.

This behavior creates uncertainty when attempting to perform idempotent restores or partial data updates using standard management commands.

• Does loaddata support any undocumented flags to override existing primary keys?
• Is there a recommended approach to achieve "upsert" behavior using built-in serialization tools?