Re: debugging prepared statements

From: Richard Welty <rwelty(at)averillpark(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: debugging prepared statements
Date: 2003-02-09 14:10:41
Message-ID: E18hsAL-00084z-00@skipper.averillpark.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Sun, 9 Feb 2003 04:31:19 -0500 (EST) Kris Jurka <books(at)ejurka(dot)com> wrote:

>
> >>From your original message it appears that either update_core_variables
> should be set to one less, or you should use field_index++ instead of
> ++field_index.

i investigated that. the discrepancy is by more than one, and the parallel,
generally similar insert code is working properly. if both were broken, i'd
agree, but in this case...

> You might also consider updating the JDBC driver at some point. The
> Statement.toString method was recently corrected to display the actual
> statement you're working on. This hasn't made it into any of the
> prebuilt jar files on jdbc.postgresql.org, but perhaps soon.

lacking time to pursue this right now, i've retained the working prepared
statement for select (that being the only way to bring arrays in), but have
bagged the prepared statemens for output. i'll try again when the prebuilt
jars are updated.

richard
--
Richard Welty rwelty(at)averillpark(dot)net
Averill Park Networking 518-573-7592
Unix, Linux, IP Network Engineering, Security

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Michael Adler 2003-02-09 17:08:05 Re: patch for COPY
Previous Message Kris Jurka 2003-02-09 09:31:19 Re: debugging prepared statements