[Pljava-dev] Using JDBC in PL/Java 1.4.0: Statement.executeQuery() automatically closes the statement?

From: books at ejurka(dot)com (Kris Jurka)
To:
Subject: [Pljava-dev] Using JDBC in PL/Java 1.4.0: Statement.executeQuery() automatically closes the statement?
Date: 2008-06-04 15:34:16
Message-ID: 4846B5F8.4040609@ejurka.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pljava-dev

holger.fleischmann at manroland.com wrote:
>
> When executing SQL queries inside PL/Java functions it seems that the
> java.sql.Statement now gets automatically closed by
> Statement.executeQuery(). This leads to a SQLException: "statement is
> closed" when calling Statement.getWarnings() afterwards.

I've applied the attached patch to CVS to fix this problem. Thanks for
the complete report and test case.

Kris Jurka

-------------- next part --------------
A non-text attachment was scrubbed...
Name: dont-close-statement.patch
Type: text/x-patch
Size: 2721 bytes
Desc: not available
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20080604/a9b9dd08/attachment.bin>

In response to

Responses

Browse pljava-dev by date

  From Date Subject
Next Message Javier Sotelo 2008-06-05 02:18:04 [Pljava-dev] RE: RE: PLJava (64-bit) Build Error: JNI_CreateJavaVM‏
Previous Message Kris Jurka 2008-06-04 15:22:19 [Pljava-dev] /usr/local/lib/pljava/pljava.so: undefined symbol: SetUserId