db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1235) Move isPoolable() and setPoolable() from PreparedStatement to Statement
Date Sat, 29 Apr 2006 15:11:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1235?page=all ]

Dyre Tjeldvoll updated DERBY-1235:

    Attachment: derby-1235.v3.diff

The failure seen by Knut Anders was caused by not initializing the isPoolable variable in
one of the PreparedStatement constructors on the client side. Since then, I have also learned
that BrokeredXXXStatements40 need to implement (override) the xPoolable methods.

I'm attaching a third patch (v3) that addresses the above issues, and also adds a new junit-test
to test these methods for BrokeredXXXStatements (jdbc4/XA40Tests.java).

Ran derbyall and jdbc4 in embedded and DerbyNetClient successfully.

Please review.

> Move isPoolable() and setPoolable() from PreparedStatement to Statement
> -----------------------------------------------------------------------
>          Key: DERBY-1235
>          URL: http://issues.apache.org/jira/browse/DERBY-1235
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Versions:
>     Reporter: Rick Hillegas
>     Assignee: Dyre Tjeldvoll
>      Fix For:
>  Attachments: derby-1235.v1.diff, derby-1235.v1.stat, derby-1235.v2.diff, derby-1235.v2.stat,
derby-1235.v3.diff, derby-1235.v3.stat, derbyall_report.v1.txt, derbyall_report.v3.txt
> An upcoming release of jdk1.6 will move isPoolable() and setPoolable() from PreparedStatement
to Statement. We should conform.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message