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 originally written if you later change what the save method does).
Andrew On Fri, Dec 20, 2013 at 4:15 PM, Val Neekman <[email protected]> wrote: > 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" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CADy_H8ERxnyrzf5UGOTPt1%3DUmj46himOBJ3w%2BBrxL49u_E3qyA%40mail.gmail.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1ura0utpBXaQ9armeYwRRbM6eCQYWiMecYuUpMCj94DuCg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
