Received: from digitaldeck.com (adsl-63-193-108-106.dsl.snfc21.pacbell.net [63.193.108.106]) by hub.org (8.10.1/8.10.1) with ESMTP id e6PKB0h89147 for ; Tue, 25 Jul 2000 16:11:01 -0400 (EDT) Received: from digitaldeck.com (localhost.digitaldeck.com [127.0.0.1]) by digitaldeck.com (8.9.3/8.9.3) with ESMTP id NAA09987; Tue, 25 Jul 2000 13:10:38 -0700 (PDT) (envelope-from mudie@digitaldeck.com) Message-Id: <200007252010.NAA09987@digitaldeck.com> To: Jim Caley cc: pgsql-interfaces@postgresql.org Subject: Re: JDBC DateTime broken in postgresql-7.02? In-reply-to: Your message of "Mon, 24 Jul 2000 21:28:28 EDT." <397CED3C.BB3EF947@chesco.com> Reply-To: mudie@digitaldeck.com X-URL: http://www.digitaldeck.com Date: Tue, 25 Jul 2000 13:10:38 -0700 From: David C Mudie X-Archive-Number: 200007/185 Jim Caley writes: >Also, Peter Mount -- replying to a post by Vincent Trussart -- mentioned >that this has been fixed (see his message below mine), assuming this is >your problem. I'm not sure where to get his fix... CVS perhaps?? I fetched fresh CVS sources and rebuilt postgresql.jar, both with and without your suggested patch, and I still see the same errors. I will dig into the JDBC calls and see if I can figure out what is going on. Thanks for the pointers! David