Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0JIDP037486 for ; Fri, 19 Jan 2001 13:13:25 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0JIDNJ09384; Fri, 19 Jan 2001 13:13:23 -0500 (EST) To: Mindaugas Idzelis cc: pgsql-interfaces@postgresql.org Subject: Re: bug in ODBC driver (and fix) In-reply-to: References: Comments: In-reply-to Mindaugas Idzelis message dated "Fri, 19 Jan 2001 12:49:14 -0500" Date: Fri, 19 Jan 2001 13:13:23 -0500 Message-ID: <9381.979928003@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/217 X-Sequence-Number: 835 Mindaugas Idzelis writes: > If it was fixed in 7.0.3, it has not yet been fixed in 7.1beta3. Oh? I'm quite sure there is no reference to int4out in ODBC now. Look for yourself if you don't believe me. That patch was applied to the main branch back in August. Are you sure you are using a driver built from the current ODBC sources, and not 7.0.2 or earlier? > Also, what is wrong with the following sql query? > create unique index primary on tablename ( tableid ); PRIMARY is an SQL reserved word. regards, tom lane