On Nov 25, 2007 6:24 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Hi Florent, > > Just realised we'd gone quiet on this thread... > > >humm What bothers me is that I already get this comportement when > >running my query program from a Linux host (using pyodbc same version) > >but need the above mentioned patch on a windows host so there is > >definitely a different behavior. > > > > > Is this a difference in PyODBC or SQLAlchemy? I suspect the former, but > good if you can confirm.
the diff is in SA. Please look at my last patch to see why. This is because the support unicode flag is controlled by the test: supports_unicode = sys.maxunicode == 65535 and on Linux (mine at least) is equals to false, but on Windows it equals to True... my patch makes this flag always false on Windows and then all works as intended Florent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
