Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (8.11.3/8.11.1) with SMTP id f493ihA73073 for ; Tue, 8 May 2001 23:44:43 -0400 (EDT) (envelope-from Inoue@tpf.co.jp) Received: (qmail 8288 invoked from network); 9 May 2001 03:44:38 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.10.0.100.in-addr.arpa with SMTP; 9 May 2001 03:44:38 -0000 Received: from tpf.co.jp (3d_note1 [126.0.1.61]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id MAA02338; Wed, 9 May 2001 12:44:37 +0900 (JST) Message-ID: <3AF8BD3E.BE32AA0A@tpf.co.jp> Date: Wed, 09 May 2001 12:45:02 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Bruce Momjian CC: Keith Millard , PostgreSQL odbc list Subject: Re: Re: [INTERFACES] Postgres odbc driver bug References: <200105090324.f493Oio22886@candle.pha.pa.us> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200105/55 X-Sequence-Number: 444 Bruce Momjian wrote: > > > > Agreed. I mentioned to Keith I was going to clean it up before > > > application. Here is the cleaned up patch. > > > > > > Hiroshi, what do you think? > > > > > > > Hmm that's not what I mean. The patch essentially means > > that the STMT_PREMATURE state is unnecessary. Well why is > > the concept *PREMATURE* introduced ? What meaning does the > > stuff related to the concept *PREMATURE* have ? IMHO we > > have to reconsider from the first. > > Oh, so you need Keith to explain the patch. OK. > I got the following mail from Keith personally about 10 hours ago. I don't like the temporary fix. It also loses the advantge of *PREMATURE* handling. [A part of his mail] > I'm not saying that our fix is the long-term solution > to this problem but it does demonstrate the issue we > found and a possible fix. What we were not sure of > is what other ramifications are there with the fix we made. regards, Hiroshi Inoue