I'm not so sure it's really an issue with the MSSQLCompiler -- ISTM that the query would run OK "naked" -- it's the way the mapper seems to wrap it (specifically, the way that it uses the query alias on the outer query instead of the inner query) that causes the problem.
On 5/11/07, Paul Johnston <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Both queries are complaining because MSSQL insists that all derived > > tables (that is, subselects used as tables) be aliased with an "AS > > xxxx" clause. > > Just so you know, providing a hack in MSSQLCompiler to do this > automatically is on my todo list. > > I did have a go at it, but the obvious simple solution didn't quite work. > > Paul > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
