Databases
StackOverflow2013
Postsdbo
POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
    primarykey
    data
    text
    <p>I'm having a bit of trouble successfully using pyodbc on Debian Lenny (5.0.7). Specifically, I appear to be having trouble fetching NVARCHAR values (not a SQL Server expert, so go easy on me :) ).</p> <p>Most traditional queries work OK. For instance, a count of rows in table1 yields</p> <pre><code>cursor.execute("SELECT count(id) from table1") &lt;pyodbc.Cursor object at 0xb7b9b170&gt; &gt;&gt;&gt; cursor.fetchall() [(27, )] </code></pre> <p>As does a full dump of ids</p> <pre><code>&gt;&gt;&gt; cursor.execute("SELECT id FROM table1") &lt;pyodbc.Cursor object at 0xb7b9b170&gt; &gt;&gt;&gt; cursor.fetchall() [(0.0, ), (3.0, ), (4.0, ), (5.0, ), (6.0, ), (7.0, ), (8.0, ), (11.0, ), (12.0, ), (18.0, ), (19.0, ), (20.0, ), (21.0, ), (22.0, ), (23.0, ), (24.0, ), (25.0, ), (26.0, ), (27.0, ), (28.0, ), (29.0, ), (32.0, ), (33.0, ), (34.0, ), (35.0, ), (36.0, ), (37.0, )] </code></pre> <p>But a dump of names (again, of type NVARCHAR) does not</p> <pre><code>&gt;&gt;&gt; cursor.execute("SELECT name FROM table1") Traceback (most recent call last): File "&lt;stdin&gt;", line 1, in &lt;module&gt; pyodbc.ProgrammingError: ('42000', '[42000] [FreeTDS][SQL Server]Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. (4004) (SQLExecDirectW)') </code></pre> <p>... the critical error being </p> <p><strong>pyodbc.ProgrammingError: ('42000', '[42000] [FreeTDS][SQL Server]Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. (4004) (SQLExecDirectW)')</strong></p> <p>This is consistent across tables.</p> <p>I've tried a variety of different versions of each, but now I'm running unixODBC 2.2.11 (from lenny repos), FreeTDS 0.91 (built from source, with <code>./configure --enable-msdblib --with-tdsver=8.0</code>), and pyodbc 3.0.3 (built from source). </p> <p>With a similar combination (unixODBC 2.3.0, FreeTDS 0.91, pyodbc 3.0.3), the same code works on Mac OS X 10.7.2.</p> <p>I've searched high and low, investigating the solutions presented <a href="http://www.seanelavelle.com/2011/07/30/pyodbc-and-freetds-unicode-ntext-problem-solved/" rel="noreferrer">here</a> and <a href="http://www.ubuntitis.com/?p=64" rel="noreferrer">here</a> and recompiling different versions of unixODBC and FreeTDS, but still no dice. Relevant configuration files provided below:</p> <pre><code>user@host:~$ cat /usr/local/etc/freetds.conf #$Id: freetds.conf,v 1.12 2007/12/25 06:02:36 jklowden Exp $ # # This file is installed by FreeTDS if no file by the same # name is found in the installation directory. # # For information about the layout of this file and its settings, # see the freetds.conf manpage "man freetds.conf". # Global settings are overridden by those in a database # server specific section [global] # TDS protocol version tds version = 8.0 client charset = UTF-8 # Whether to write a TDSDUMP file for diagnostic purposes # (setting this to /tmp is insecure on a multi-user system) ; dump file = /tmp/freetds.log ; debug flags = 0xffff # Command and connection timeouts ; timeout = 10 ; connect timeout = 10 # If you get out-of-memory errors, it may mean that your client # is trying to allocate a huge buffer for a TEXT field. # Try setting 'text size' to a more reasonable limit text size = 64512 # A typical Sybase server [egServer50] host = symachine.domain.com port = 5000 tds version = 5.0 # A typical Microsoft server [egServer70] host = ntmachine.domain.com port = 1433 tds version = 8.0 [foo] host = foo.bar.com port = 1433 tds version = 8.0 user@host:~$ cat /etc/odbc.ini [foo] Description = Foo Driver = foobar Trace = No Database = db Server = foo.bar.com Port = 1433 TDS_Version = 8.0 user@host:~$ cat /etc/odbcinst.ini [foobar] Description = Description Driver = /usr/lib/odbc/libtdsodbc.so Setup = /usr/lib/odbc/libtdsS.so CPTimeout = CPReuse = </code></pre> <p>Any advice or direction would be very much appreciated!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStcdyl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
      1. UStcdyl
      1. VTBountyStart
    2. VO
      singulars
      1. POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm getting same thing. Works with FreeTDS/unixODBC on mac and FreeBSD, but no go on CentOS
      singulars
      1. POpyodbc/FreeTDS/unixODBC on Debian Linux: issues with TDS Version
      1. USJustin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload