RE: bug in ODBC driver (and fix)

From: Mindaugas Idzelis <mai3116(at)ritvax(dot)isc(dot)rit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: RE: bug in ODBC driver (and fix)
Date: 2001-01-19 17:49:14
Message-ID: JHELIEPMICHICPLGHHDKGEHKCAAA.mai3116@rit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces pgsql-odbc

If it was fixed in 7.0.3, it has not yet been fixed in 7.1beta3. In which
case, I have taken the source for the ODBC driver version 6.5 patched it
without the int4out() function, and compiled it. The driver is available at
http://neovintage.com/postgresODBC. This should help anyone using ODBC with
7.1beta3.

By the way. How come one of my applications (platinum erwin) does not get
any primary (or foreign) key information from the ODBC driver. When I was
using mySQL with the myODBC driver it got primary key information.

Also, what is wrong with the following sql query?
create unique index primary on tablename ( tableid );
this works:
create unique index primary2 on tablename (tableid );

it's allegedly a parse error. (in the database as well as the ODBC driver)

thank you.

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, January 19, 2001 10:45 AM
To: Mindaugas Idzelis
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] bug in ODBC driver (and fix)

Mindaugas Idzelis <mai3116(at)ritvax(dot)isc(dot)rit(dot)edu> writes:
> the int4out() function should be removed.

Yes, it should. This is fixed as of 7.0.3, IIRC.

regards, tom lane

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Lane 2001-01-19 18:13:23 Re: bug in ODBC driver (and fix)
Previous Message Tom Lane 2001-01-19 15:44:41 Re: bug in ODBC driver (and fix)

Browse pgsql-odbc by date

  From Date Subject
Next Message Tom Lane 2001-01-19 18:13:23 Re: bug in ODBC driver (and fix)
Previous Message Tom Lane 2001-01-19 15:44:41 Re: bug in ODBC driver (and fix)