Skip to Content.
Sympa Menu

freetds - RE: [freetds] Function sequence error from Linux => SQL Server 2000

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Function sequence error from Linux => SQL Server 2000
  • Date: Thu, 29 Apr 2004 11:42:37 +0200

...
>
> Two final clues:
> (1) If I use the Python interpreter to instantiate my DB
> connection and
> call the stored procedure with the same XML data, it loads
> the data into
> the target table with no complaint.
> (2) In my script I create six or seven different connections to the
> database, each with its own cursor, so that each cursor executes only
> one thing on the SQL server. My hope was to reduce overhead by
> permitting each cursor to prepare just one statement. Now that the
> cursors are executing stored procedures rather than SQL statements,
> perhaps I should use only one connection and cursor.
>
...

Strange... I tested with latest sources (mxBase-2.0.5 and
mxCommercial-2.0.6) and I founded this code:

if (var->data_len < 256)
var->sqltype = SQL_CHAR;
else
var->sqltype = SQL_LONGVARCHAR;

(both iOBDC and unixODBC).
For long data my test code use (correctly) TEXT and data got send to
server correctly. Log you sent seem to use SQL_CHAR instead...

freddy77




Archive powered by MHonArc 2.6.24.

Top of Page