Unfortunately, dumping SQL Server (in favor of Oracle) may not be an
option, due to management concerns and other factors. Still working on it.
However, I did manage to get this working with pymssql. Apparently, there
is a bug with pyodbc and 64-bit python
(see
Looking at that issue, and suggested fix... I think you're best going with
that route. the stock apple Python is usually pretty bad, and it seems to
be the compile settings apple selected, not python. apple's version is
often VERY out of date and has some weird settings. It's screwed me and
Hi Jonathan,
For the record, in my current setup, I installed python via Homebrew. Prior
to that, I was using the Apple build of python, which would have been the
32-bit version that came with Lion.
Greg--
On Mon, Sep 8, 2014 at 6:31 PM, Jonathan Vanasco jonat...@findmeon.com
wrote:
Looking at
SQL Server and unix, many things can change:
- UnixODBC version
- FreeTDS version (0.82 and 0.91 have *extremely* different behaviors)
- FreeTDS configuration
The first place I'd look in this case would be your freetds.conf, you probably
need to configure the character set correctly in there.
Thanks. I forgot to mention that I had tried adding the encoding scheme to
freetds.conf. I also tried other encoding schemes, all to no avail. I may
try pymssql tomorrow to see what that does. I would have tried mxodbc, but
I am not about to pay $379 for a driver. I may also see if I can get
I think I am going to dump SQL Server and just go with Postgres. Much
easier, and less of a headache. Fortunately, we are not yet in production.
Thanks!
Greg--
On Thu, Sep 4, 2014 at 8:31 PM, Horcle g...@umn.edu wrote:
Thanks. I forgot to mention that I had tried adding the encoding scheme
