anyway, this is fixed again by applying my original patch that I thought I wasn't going to need, so thanks for the very nice testing !
On Apr 3, 2012, at 9:39 AM, Michael Bayer wrote: > OK so from the ORM perspective, you're building column_property objects > composed from others right ? > > > On Apr 3, 2012, at 2:59 AM, Christoph Rauch wrote: > >> Hello Michael, hello List, >> >> thanks for your previous patch. Most queries of that type do work now. >> >> I am sorry but I have to inform you that I stumbled upon another query which >> used these selects in a nested fashion, that triggered the bug. :-} >> >> cheers, >> Christoph >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/sqlalchemy/-/0yb7gY4d_BAJ. >> To post to this group, send email to [email protected]. >> 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. >> <deep_deannotate_and_aliased_tables.py> > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to [email protected]. > 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. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
