Date: Fri, 19 Jan 2001 12:49:14 -0500
From: Mindaugas Idzelis <mai3116@ritvax.isc.rit.edu>
Subject: RE: bug in ODBC driver (and fix)
In-reply-to: <8536.979919081@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Message-id: <JHELIEPMICHICPLGHHDKGEHKCAAA.mai3116@rit.edu>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal

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@sss.pgh.pa.us]
Sent: Friday, January 19, 2001 10:45 AM
To: Mindaugas Idzelis
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] bug in ODBC driver (and fix)


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

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

			regards, tom lane