Yeah, I see that now, thanks. I checked in a small clarification to the mapper documentation in r3718 about this. It would be easier if you would open the ticket for me if you don't mind. Trac seems to hate me and won't let me stay logged in long enough to save a ticket (does anybody else run into that?).
On 11/2/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > you need to have "None" for the tables in all the subclass mappers > (SecUser, SecRole, SecFilter, etc.) . this is one of those cases > where SQLAlchemy should really be raising some kind of error, im > surprised its trying to chug along with that (also that its not trying > to make some bizarre self-referential join on the table....). id > actually want to file a bug report that this didn't raise a whole > bunch of errors and alarms... > > On Nov 2, 5:23 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote: > > Please have a look at the attached testcase that mixes single-table > > polymorphic inheritance, primaryjoin overides on the relation() and a > > secondary table. > > > > SA seems to add a WHERE clause to filter for the polymorphic type on > > relations that it calculates, but forgets to add it for the test case. > Is > > this supposed to work, or is it necessary to specify the filter in the > > relation()? > > > > Thx, > > Rick > > > > poly1m.py > > 4KDownload > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
