Hi Michael, it looks fine now. Thanks a lot! By the way, your abilities are rather impressive... Best regards Klaus
On 7 Nov., 01:55, Michael Bayer <[EMAIL PROTECTED]> wrote: > indeed its extremely difficult to reproduce this one, and while it was > pretty clear what caused it i found it impossible to work up a simpler > set of tables that could create all the conditions necessary to > produce an invalid query...in any case the offending code was some > stuff that wasnt even needed so its removed in r3746. > > On Nov 6, 2007, at 9:40 AM, klaus wrote: > > > > > Hi all, > > when I try to build up a complicated query like this: > > > query = session.query(Class) > > query = query.filter_by(...).add_entity(...).join(...) > > count = query.count() > > query = query.add_entity(...).join(...).order_by(...) > > print query.all() > > > the last statement fails due to a broken SELECT. The error disappears > > if I remove the line with the query.count(). > > > The following is an example to reproduce the behavior. I'm sorry that > > it is so complicated, but a certain complexity seems to be necessary > > to trigger the bug. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
