On Apr 6, 2007, at 8:19 PM, [EMAIL PROTECTED] wrote:
> > btw whats the reasoning/rational behind the above default behaviour? i think it is often unexpected behavior, particularly for a query that returns rows between say table A and table B, where some of the rows contain nulls for the "B" columns. if the primary key is composite between A and B, distinct entities get created twice for each A row, one corresponding to the "B" columns present, one corresponding to the "B" columns not present. we have one polymorphic test that fails with this option turned on - test/orm/ inheritance3.py. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
