3đź‘Ť
No you’re not. save() is NOT called by loaddata, by design (its way more resource intensive, I suppose). Sorry.
EDIT: According to the docs, pre-save is not called either (even though apparently it is?).
Data is saved to the database as-is, according to https://docs.djangoproject.com/en/dev/ref/django-admin/#what-s-a-fixture
2đź‘Ť
I’m doing something similar now – I need a second model to have a parallel entry for each of the first model in the fixture. The second model can be enabled/disabled, and has to retain that value across loaddata
calls. Unfortunately, having a field with a default value (and leaving that field out of the fixture) doesn’t seem to work – it gets reset to the default value when the fixture is loaded (The two models could have been combined otherwise).
So I’m on Django 1.4, and this is what I’ve found so far:
- You’re correct that
save()
is not called. There’s a specialDeserializedObject
that does the insertion, by callingsave_base()
on the Model class – overridingsave_base()
on your model won’t do anything since it’s bypassed anyway. - @Dave is also correct: the current docs still say the pre-save signal is not called, but it is. It’s behind a condition:
if origin and not meta.auto_created
origin
is the class for the model being saved, so I don’t see why it would ever be falsy.meta.auto_created
has been False so far with everything I’ve tried, so I’m not yet sure what it’s for. Looking at the Options object, it seems to have something to do with abstract models.- So yes, the
pre_save
signal is indeed being sent.
- Further down, there’s a
post_save
signal behind the same condition that is also being sent.
Using the post_save signal works. My models are more complex, including a ManyToMany on the “Enabled” model, but basically I’m using it like this:
from django.db.models.signals import post_save
class Info(models.Model):
name = models.TextField()
class Enabled(models.Model):
info = models.ForeignKey(Info)
def create_enabled(sender, instance, *args, **kwards):
if Info == sender:
Enabled.objects.get_or_create(id=instance.id, info=instance)
post_save.connect(create_enabled)
And of course, initial_data.json
only defines instances of Info
.
- Deploying existing Django app on Heroku
- Live notification/chat in django
- How should I go about learning Python?
- Can I delete the django migration files inside migrations directory
- Missing custom header with django, nginx and gunicorn