I've been monkeying with trunk some more this afternoon, and since I replaced assign_mapper with a local version that doesn't monkeypatch the 'options' query into the domain model, I can't reproduce the inheritance error either, so I'm pretty sure that I was seeing two symptoms of the same problem. I'm not using polymorphic unions, though.
JP On Jan 24, 4:45 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > 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. > > > JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
