Re: South data-migration and custom save() method

That's what i do in south, sometimes. But sometimes you have a bigger table with initial data, like a table with predefined prices. and it wouldn't be that cool to instantiate 20.000 or more prices manually. Am Sonntag, 22. Dezember 2013 12:06:02 UTC+1 schrieb Andrew Godwin: > > It won't load

Re: South data-migration and custom save() method

It won't load initial_data fixtures - those are being deprecated for migrated apps - but you could still call loaddata with a custom one, I guess. I'd personally recommend moving away from fixtures and just instantiating objects directly using the ORM inside data migrations. Andrew On Sat, Dec

Re: South data-migration and custom save() method

I didn't found anything in the docs... So... could I stil load a fixture with a migration? Like here: http://south.readthedocs.org/en/latest/fixtures.html Am Freitag, 20. Dezember 2013 17:41:22 UTC+1 schrieb Andrew Godwin: > > This will also be true for django.db.migrations; there's no way we

Re: South data-migration and custom save() method

Yep, this is what I currently do and I was just hoping for a cleaner solution in 1.7. That's all. Thanks for django.db.migrations Andrew. Val On Fri, Dec 20, 2013 at 11:41 AM, Andrew Godwin wrote: > This will also be true for django.db.migrations; there's no way we can

Re: South data-migration and custom save() method

This will also be true for django.db.migrations; there's no way we can serialise save methods as part of the model for later use in migrations. If you want to use complex save logic in migrations, you'll have to copy it into the migration file (which also means the migration will keep working as

South data-migration and custom save() method

South (latest) has a limitation where it ignores a custom save() method in the model class. I am wondering if that is going to be true for the new South in the core in Django 1.7? Thanks, Val -- You received this message because you are subscribed to the Google Groups "Django developers"