[sqlalchemy] Re: Concrete inheritance woes

2008-04-29 Thread Gaetan de Menten
On Mon, Apr 28, 2008 at 10:33 PM, Michael Bayer [EMAIL PROTECTED] wrote: pjoin = polymorphic_union(...) pjoin2 = polymorphic_union(...) employee_mapper = mapper(Employee, pjoin, polymorphic_on=pjoin.c.type) manager_mapper = mapper(Manager, managers_table, inherits=employee_mapper,

[sqlalchemy] Re: Concrete inheritance woes

2008-04-29 Thread Gaetan de Menten
On Tue, Apr 29, 2008 at 12:11 PM, Gaetan de Menten [EMAIL PROTECTED] wrote: On Mon, Apr 28, 2008 at 10:33 PM, Michael Bayer [EMAIL PROTECTED] wrote: In any case the unit tests which you were working from (im guessing test/orm/inheritance/concrete.py) should be patched to include this

[sqlalchemy] Re: Concrete inheritance woes

2008-04-29 Thread az
g'day Gaetan u could try my tests and play with DB_inheritance=concrete to see my experience so far with dbcook (not documented i know but works4me) and its tests. also u can look up the mailgroup history for my own concrete-related complaints... most of them have hit unimplemented parts of

[sqlalchemy] Re: Concrete inheritance woes

2008-04-29 Thread Michael Bayer
On Apr 29, 2008, at 2:32 PM, [EMAIL PROTECTED] wrote: btw, if Mike is about delving into all this now, i think i have some time to look around it, at least move onto with_polymorphic. if you're going to deal with future functionality, go work with the user_defined_state branch for now,

[sqlalchemy] Re: Concrete inheritance woes

2008-04-28 Thread Michael Bayer
On Apr 28, 2008, at 12:07 PM, Gaetan de Menten wrote: pjoin = polymorphic_union({ 'manager':managers_table, 'engineer':engineers_table, 'hacker':hackers_table }, 'type', 'pjoin') mapper(Company, companies, properties={ 'engineers':relation(Engineer,