[sqlalchemy] Re: Concrete Inheritance problem

2007-11-19 Thread sdobrev
if it's about concrete inheritance, then employee contains ALL info it needs, that is, a full copy of person + whatever else is there, and is completely independent from person table. so for that case, a) foregn key is not needed b) inserting in employee_tbl will never insert stuff in

[sqlalchemy] Re: Concrete Inheritance problem

2007-11-19 Thread Partha
Thank you! . That worked great.. Partha On Nov 19, 2:41 pm, [EMAIL PROTECTED] wrote: if it's about concrete inheritance, then employee contains ALL info it needs, that is, a full copy of person + whatever else is there, and is completely independent from person table. so for that case,