Thanks Mike, MSSQL itself supports Unicode. The issue is with one of the supported MSSQL access modules, pymssql. It's based on the old DBlib, which seems to actively hate Unicode. As the various DBAPI interfaces for the MSSQL modules are already kept in separate Dialects, the scheme sounds like it will work fine.
On 3/29/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > Theres a hook I added for "supports_unicode_statements()" on Dialect > that will tell the engine to stringify the queries before being > sent. Oracle implements one that returns False, for example. just > add one in and have it return false. > > but, I thought MS-SQL supports unicode column names ? hows that > going to work ? > > > On Mar 28, 2007, at 10:49 PM, Rick Morrison wrote: > > > Mike, I'm seeing som breaking of MSSQL / pymssql that I think might > > be caused by the latest unicode stuff. > > The statements themselves are beginning to be issued in unicode > > when a query is constructed in the ORM. > > > > Where is an appropriate place for the dialect to intercept the call > > to the DB-API just before it's issued so that it can convert to str > > ()? I've tried do_execute and _execute so far. > > > > Rick > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
