[sqlalchemy] Re: Column name override with a relation requiring a primaryjoin

2008-05-29 Thread Michael Bayer
On May 29, 2008, at 11:58 AM, Brad Wells wrote: Thank you very much for your help. The post_update=True addition is what I was missing. The test case I was using was c1.created_by = c1 where created_by was previously null. (c1 having previously been saved and flushed) This seems to be

[sqlalchemy] Re: Column name override with a relation requiring a primaryjoin

2008-05-28 Thread Michael Bayer
this is a many-to-one self-referential relationship. the remote_side attribute is needed on both relations() to establish this, and the uselist=False is not needed (its hiding the actual error here). See the docs on self-referential mappings. On May 28, 2008, at 6:11 PM, kremlan wrote: