I finally got the encoding to work. I moved from linux to windows,
and now the encoding works with both pymssql and pyodbc.
So it had to do with using FreeTDS. I experimented with FreeTDS.conf
to use version 7.0 and 8.0 and various charsets, but could not get it
to work, so I'll man up and use w
Last I heard, pyodbc was working on any POSIX system that supports odbc
(most likely via unixodbc or iodbc)
http://sourceforge.net/projects/pyodbc/
-- check out the supported platforms
On 4/11/07, Marco Mariani <[EMAIL PROTECTED]> wrote:
>
>
> Rick Morrison wrote:
> > ...and while I'm making t
Rick Morrison wrote:
> ...and while I'm making this thread unnecessarily long, I should add
> that while pymssql may not understand Unicode data, the pyodbc DB-API
> interface does. Thanks to recent work by Paul Johnston, it's on
> fast-track to becoming the preferred MSSQL db-api for SA.
Since h
...and while I'm making this thread unnecessarily long, I should add that
while pymssql may not understand Unicode data, the pyodbc DB-API interface
does. Thanks to recent work by Paul Johnston, it's on fast-track to becoming
the preferred MSSQL db-api for SA.
On 4/10/07, Rick Morrison <[EMAIL PR
Arghh, that last bit should be chr(146), not ord(146)
On 4/10/07, Rick Morrison <[EMAIL PROTECTED]> wrote:
>
> You've got hi-bit characters in your data. MSSQL with pymssql will store
> this, but not understand it.
>
> You most likely are looking for a "normal" ASCII apostrophe (i.e. ord(39))
>
You've got hi-bit characters in your data. MSSQL with pymssql will store
this, but not understand it.
You most likely are looking for a "normal" ASCII apostrophe (i.e. ord(39))
instead of the hi-bit version you've got.
to get it, try ${str}.replace(ord(146), "'")<-- that last bit is a
single
