On Feb 12, 12:05 pm, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote:
> All I know is that this problem was supposed to be fixed in SQLAlchemy
> 0.4.1 (seehttp://www.sqlalchemy.org/CHANGES). If you are using an
> earlier version, upgrading is probably the solution, otherwise, there
> is still a bug somewhere which should be reported with a test case.
Thanks a lot, upgrading did the trick.
Cheers,
-- Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SQLElixir" 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/sqlelixir?hl=en
-~----------~----~----~----~------~----~------~--~---
