Problem fetching NTEXT and NVARCHAR data about pyodbc

[GoogleCodeExporter]

OK, this is something wierd.  It works on Windows just fine, so there is 
something
about the combination of Easysoft and Linux.

Is it possible to get an ODBC trace of the 2.1.2 that fails and the 2.0.58 that 
works
so I can compare them?

Original comment by mkleehammer on 12 Dec 2008 at 7:18

• Changed state: Investigating

[GoogleCodeExporter]

Please find attached.

Original comment by [email protected] on 15 Dec 2008 at 9:42

Attachments:

• unixodbc.zip

[GoogleCodeExporter]

I'm not ignoring this, but I have not been able to get my Linux system to 
connect to
my test SQL Server instance.  Networking issues w/ Vista & Windows 7.  sigh.

The traces looked nearly identical, so it is clearly something in the 
GetDataString
function.  Unfortunately the newer function is more correct.  I'm concerned 
there is
a problem with the driver.

Original comment by mkleehammer on 18 Mar 2009 at 3:51

[GoogleCodeExporter]

I'm using 
- pyodbx-2.1.6
- unixODBC 2.2.12
- python2.6
on a Red Hat Enterprise (32)
to talk to SQL Server 2005.

I just want to comment that I think you are right that this is a driver problem.
I initially tested pyodbc using Easysoft SQL Server ODBC driver 1.1.4 and had 
the
same problem with Tim. Since I don't want to pay for the license ($$$$$), I 
ended up
installing FreeTDS 0.82 and found that the problem goes away. Configuration was
definitely harder for FreeTDS but the result is awesome. Hail to pyodbc and 
FreeTDS.

Original comment by [email protected] on 28 Aug 2009 at 8:50

[GoogleCodeExporter]

Original comment by mkleehammer on 1 Jan 2010 at 6:45

• Changed state: Invalid

[GoogleCodeExporter]

Original comment by mkleehammer on 21 Nov 2010 at 4:43

• Changed state: NoFix