From: | "Mike Clements" <mclement(at)progress(dot)com> |
---|---|
To: | "Kris Jurka" <books(at)ejurka(dot)com> |
Cc: | "PostgreSQL JDBC List" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Fetching generated keys |
Date: | 2007-03-06 23:35:10 |
Message-ID: | 626C0646ACE5D544BC9675C1FB81846B33894F@MAIL03.bedford.progress.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kris,
I wrote a simple test program and schema but I can't reliably reproduce
the problem. The problem I'm seeing is intermittent. When calling next()
on the result set, it sometimes throws an exception saying the DB
connection has been closed. Of course it hasn't been closed, but the
problem is now so intermittent I can't reliably reproduce it.
If I end up being able to reproduce it consistently I'll post the sample
code.
Regards,
-----Original Message-----
From: Kris Jurka [mailto:books(at)ejurka(dot)com]
Sent: Tuesday, March 06, 2007 5:42 PM
To: Mike Clements
Cc: PostgreSQL JDBC List
Subject: Re: [JDBC] Fetching generated keys
On Tue, 6 Mar 2007, Mike Clements wrote:
> 2. call executeQuery() and use the result set.
>
> If I call statement.executeQuery(), it throws an exception saying the
> connection is already closed ?!?!
>
I have no idea what you're testing, but the attached works fine for me.
Could you provide individual test cases for any and all problems you are
seeing?
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | A.M. | 2007-03-07 00:33:44 | Re: Fetching generated keys |
Previous Message | Tom Lane | 2007-03-06 23:23:58 | Re: Plan invalidation vs. unnamed prepared statements |