ok, that solves some things, i won't need those ultra-explicit selects() now. The other problem remains: union's mechanism for corresponding_column() takes ownership of all columns mentioned in the WHERE, regardless if they are from a table within the union/join, or in alias of that table. i.e. all columns mentioned in the WHERE become punion.column_name.
> > The query itself, if fixed manualy, works: > > SELECT ... > > FROM (...) as pu_human, human as humanalias > > WHERE pu_human.friend_id = humanalias.db_id AND humanalias.age > > > ? > > > > while the SA does: > > SELECT ... > > FROM (...) as pu_human > > WHERE pu_human.friend_id = pu_human.db_id AND pu_human.age > ? > > > > is it some .corresponding_column() taking ownership of too many > > things? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
