[sqlalchemy] Re: SA 0.3.4 released - Michael Bayer - com.googlegroups.sqlalchemy

11 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: SA 0.3.4 released

From	Sent On	Attachments
Michael Bayer	23 Jan 2007 11:57
Michael Bayer	23 Jan 2007 12:14
JP	24 Jan 2007 08:25
Michael Bayer	24 Jan 2007 08:41
JP	24 Jan 2007 09:12
Michael Bayer	24 Jan 2007 09:43
JP	24 Jan 2007 11:08
JP	24 Jan 2007 11:19
Michael Bayer	24 Jan 2007 12:42
Michael Bayer	24 Jan 2007 13:45
JP	24 Jan 2007 13:59

Subject:	[sqlalchemy] Re: SA 0.3.4 released
From:	Michael Bayer (mike...@zzzcomputing.com)
Date:	01/24/2007 01:45:14 PM
List:	com.googlegroups.sqlalchemy

hey jason -

someone reported an error regarding many-to-one relationships to certain polymorphic joins, which was definitely introduced in 0.3.4. ive fixed that issue in rev 2250. if your inheritance conditions use polymorphic unions, you might want to try it out and see if it resolves your other problem.

- mike

On Jan 24, 2007, at 2:19 PM, JP wrote:

(repeating my last ticket comment)

Ok, I think I've tracked this down. The error is occurring because the name of the backref is 'options', which as of r2205 is being overwritten by assign_mapper.

I'm not sure what's the right thing to do here. I don't think assign_mapper can avoid stepping on backrefs like this one, since (I think) the backref doesn't exist when assign_mapper is monkeypatching the domain model class.