fixture-seed-debug

This error occurs because loaddata uses raw=True, which bypasses auto_now_add and auto_now fields, inserting NULL. Instead of loaddata, create an ORM-based management command using update_or_create so Django populates the timestamp fields normally.

FK violations happen when fixtures load in the wrong order and child records reference parent PKs that do not exist yet. Load parent fixtures first, then child fixtures, or use an entrypoint script that handles multiple ordered passes.

This happens when the data already exists, such as re-running loaddata on a populated database. Use the --ignorenonexistent flag, wrap the load in try/except, or switch to a management command using update_or_create for idempotency.

No. Fields with auto_now_add have editable=False, and deserializers like djmoney's reject unknown fields, so adding timestamps to fixture JSON does not work. The reliable fix is an ORM-based seed command instead of loaddata.

The fixture contains a field name that does not match the model, such as updated_at versus modified_at. Inspect actual field names via a Django shell command iterating over Model._meta.get_fields() and correct the fixture.