The FreeTDS driver needs to be passed a value encoded in the encoding specified in the 'client charset' part of the odbc.ini configuration file for the data-source in question. FreeTDS will use iconv to re- encode the data in UCS-2 (which is either what is used by SQL Server or is equivalent to the encoding used by SQL Server).
I thought there was a bug in the mssql bind_processor but I just re- checked the code and don't see anything obvious. I haven't been doing any low-level SA stuff for several weeks so take this with a pinch of salt. pjjH On Jul 30, 8:28 am, Ed Singleton <singleto...@gmail.com> wrote: > On 30 Jul 2009, at 04:52, Michael Trier wrote: > > > > > Hi, > > > On Wed, Jul 29, 2009 at 1:30 PM, Ed Singleton > > <singleto...@gmail.com> wrote: > > Stupidly forgot to attach the files. > > > > What I'm trying to achieve is: > > > > 1) Ability to insert non-ascii chars into the db on Linux > > > 2) The above but for all column types (varchar, text, nvarchar, > > ntext) > > > > Absolutely any ideas will be appreciated. I'm not sure what to try > > > next. For now I'm going to document how I set up Linux. > > > Excellent. I'll dig into this tomorrow if I get a chance to see if > > I can help propel this along. > > I've put a post explaining my setup on my blog at: > > http://blog.singletoned.net/2009/07/connecting-to-ms-sql-server-from-... > > It's pretty similar to the Mac one, understandably, and it's aimed > fairly low. I'll be writing up more concise ones aimed at a higher > level audience for work. I'll also post them anywhere else that's > useful. > > Ed --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
