pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ken J. Wright <ken@ori-ind.com>
To: Byron Nikolaidis <byron.nikolaidis@home.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ODBC bind trouble with bigint
Date: Tue, 01 Feb 2000 21:48:39 -0800
Message-ID: <3.0.32.20000201214837.00877860@ren.cncware.com> (raw)

At 20:39 02/01/2000 -0500, Byron Nikolaidis wrote:
>
>
>"Ken J. Wright" wrote:
>> 
>> With Delphi 4/ODBCExpress 5.04 and psqlodbc 6.40.0008, this error occurs
>> when opening a dataset that includes an int8 column.
>> 
>> Project1        ee:dc   ENTER SQLBindCol
>>                 HSTMT               0x010b2138
>>                 UWORD                        3
>>                 SWORD                      -25 <SQL_C_SBIGINT>
>>                 PTR                0x011b7574
>>                 SDWORD                     0
>>                 SDWORD *            0x011b75ac
>> 
>> Project1        ee:dc   EXIT  SQLBindCol  with return code -1 (SQL_ERROR)
>>                 HSTMT               0x010b2138
>>                 UWORD                        3
>>                 SWORD                      -25 <SQL_C_SBIGINT>
>>                 PTR                0x011b7574
>>                 SDWORD                     0
>>                 SDWORD *            0x011b75ac
>> 
>>                 DIAG [HYC00] [Microsoft][ODBC Driver Manager] Driver
does not support
>> this parameter (0)
>> 
>> ************
>
>
>I'm thinking this has to be an odbc 3.0 compatibility problem. The
>default for odbc 2.x is that BIGINT uses a SQL_C data type of
>SQL_C_CHAR.  I tested BindCol and it worked fine.  There is no
>SQL_C_SBIGINT in odbc 2.x.   Seems to me the odbc 3.0 driver manager
>should bridge the gap and use an SQL_C_CHAR for the driver side.

The bridge does seem to fall short occasionally ;-(

>So, I don't know what to tell you.  I imagine you don't have any control
>over the SQL_C_ data type, right?  

I copied this message to the ODBCExpress people as well. It's all part of
the code that's wrapped around opening a dataset. The API can certainly be
hacked, but I'll wait until I here something back. It takes a couple/few
days, but they usually have a good reply.

Ken





view thread (3+ messages)

Message-ID: <3.0.32.20000201214837.00877860@ren.cncware.com>
Permalink:  ../3.0.32.20000201214837.00877860@ren.cncware.com/
Also on:    postgresql.org/message-id/3.0.32.20000201214837.00877860@ren.cncware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: ken@ori-ind.com, byron.nikolaidis@home.com
  Subject: Re: [INTERFACES] ODBC bind trouble with bigint
  In-Reply-To: <3.0.32.20000201214837.00877860@ren.cncware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox