I've been using 0.3 for a while and everything was peachy. Now I'm trying to update the framework, which has 0.5 as requirement.
Besides the syntax change (which cost my many hours to rewrite all the code), I now get a "can't adapt" error every time there's a datetime value involved. Do I really have to recode every occurence of column >= datetime.now() to column >= datetime.now().isoformat() ??? Why can't SA handle a simple datetime object anymore? It's not a database issue since the database returns the values quite happily - just SA can't make any sense out of it anymore. Database is postgresql. --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
