On Nov 10, 2008, at 5:34 PM, [EMAIL PROTECTED] wrote:
> > On Mon, 10 Nov 2008 at 17:19, Michael Bayer wrote: >> Possibly. The "fragility" here is that you are relying on a model >> that isn't actually implemented here, i.e. that your application is >> written around a table inheritance assumption when that is not >> actually the case - the "extended" tables may or may not have a row >> present for a corresponding base row. It would likely be more >> straightforward to implement a non-inheriting system. > > OK. Is there a way to do that and still have the (for example) > ExtendedPublication object inherit from the Publication object, or do > I need to switch to an object composition scheme? In which case > pre-populating the extended tables may be a lot easier :) you should go with composition since its simpler. After that, if there's something missing that inheritance provides we can take a look at that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
