Hi Chris, Chris Morgan schrieb:
I think the answer is that currently it's a separate class? I would much prefer the structure of the inheritance method but can work with either. If I use the current structure and then have to (or can) switch to inheritance, how hard would the migrations be? (Would it be possible with South? I haven't used it yet. It could be done via JSON without too much difficulty, I imagine.) And how long would you expect it to take before inheritance can be used? If it's in the order of a year or more I'll just continue doing it the current way, but if it could be in in the next few months I'll work on other parts of the project first (and/or wait).
I am not so involved in Satchmo development by itself, but after reading http://docs.djangoproject.com/en/1.2/topics/db/models/#multi-table-inheritance it seems as if django's inheritence will result in nearly the same database structure. The foreign-key-attribute to Product will be created automatically.
So I would not expect the change to be very problematic, there would nearly be no migration on database level required.
Yours, Johannes -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
