From: Ben S. <sch...@pr...> - 2005-02-12 19:51:56
|
Oleg, I presume that SQLObject-trunk_postgres-7.2.tar.bz2 is the latest code that I should be testing my inheritence code on? If so then I'm still seeing the same problem as before. Whenever I create a new instance of the child class it insists that its primary key be a sequence rather than using the primary key from the parent class and enforcing the 1-1 relationship. I'm going to try to d/l all the test stuff today and come up with some explicit code to demonstrate this but, what I posted before (modified to fit the new requirements) will still break the same way. Do you all test under Postgres as well or only under SQLLite? thanx & later, Ben Scherrey Oleg Broytmann wrote: >I've forgotten to add inheritance subpackage to setup.py. This is now >fixed. Also I committed a minor optimization - do not pass parent's >values to child's _create() to avoid UPDATEing the parent after INSERT. >These were the last minor problems in the inheritance that I was aware >of. Now I consider the inheritance patch to be fully integrated. > >Oleg. > > |