Hi > Is there any chance someone can look at ticket 973? > http://www.sqlalchemy.org/trac/ticket/973 > > This is quite important to me, hitting the bug with a production app. > I've got a very hacky fix, which just disables the table aliasing, but > I don't think that's good enough to commit. I have looked at this a > few times and not figured it out, so any help would be appreciated.
It would be helpful if you would put up a test case showing the failing. Some of these types of tickets sit there because there isn't enough information provided to know exactly what is going on and where the failing is at. Sure we can look at the resultant output and see where the problem is, but if we have to try to back our way in to how you arrived at that it likely will not see much movement. Thanks, Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
