On Wed, Nov 24, 2010 at 8:04 PM, Johannes Bornhold <j...@bo-tech.de> wrote:
> 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-inheritanceit > 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. > Thanks for that; it looks to be good news for migration in particular; however due to the confusion on the topic, when it comes to existing *usage*I'd like a Satchmo-specific answer. It seems from that to be that if you had class CustomProduct(Product), in places where you have Product you could use p.customproduct, but then I'm not at all certain about how it would work with these type-specific templates - still p.customproduct, or just p as a CustomProduct? And how does it work with the _get_subtype stuff? I think the Django answer is overly simple for application here for these reasons. Then also, there's the way in 0.9.1 "custom", "downloadable" etc. have been split into subtypes... should look at them. -- Chris Morgan -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to satchmo-us...@googlegroups.com. To unsubscribe from this group, send email to satchmo-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.