PyODBC accepts unicode strings (and by that I mean Python unicode, u'some string') directly on most platforms. No "N" character is needed (unless PyODBC or the odbc driver does this behind the scenes). Our MSSQL dialect does detect certain builds where this is not possible and instead encodes to utf-8 or whatever encoding is configured on the engine before passing in unicode strings.
On Jun 18, 2009, at 8:30 AM, cristiroma wrote: > > Hello, I have a question regarding SQLAlchemy(0.4) with PyODBC, > SQLServer 2008. > I want to insert Unicode data and query values should be prefixed with > 'N' like INSERT INTO test VALUES(N'Сърцето и черният й дроб'). Is this > possible with SA 0.4? > > The main problem with SQL Server is that needs explicit 'N' prefix to > string values containing Unicode and I cannot find a way to insert > Unicode data other than modifying SA queries. Before digging into this > I want to make sure there is no other way. > > Best regards, > Cristian. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
