Jonathan LaCour wrote: > It appears to me that MySQL doesn't like it when you don't specify a > FROM in the subselect, whereas PostgreSQL and SQLite don't care.
Responding to myself, I have solved the problem. As it turns out, you can force SQLAlchemy to generate a FROM for the subselect by passing the `correlate=False` keyword argument to the subselect. Is there any reason that `correlate` defaults to `True`? Should it be automatically flipped to `False` for subselects? -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
