You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2012/05/16 14:43:02 UTC
[jira] [Created] (DERBY-5765) Embedded doesn't clear warnings on
ResultSet when moving to next row
Knut Anders Hatlen created DERBY-5765:
-----------------------------------------
Summary: Embedded doesn't clear warnings on ResultSet when moving to next row
Key: DERBY-5765
URL: https://issues.apache.org/jira/browse/DERBY-5765
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.8.2.2
Reporter: Knut Anders Hatlen
The javadoc for java.sql.ResultSet.getWarnings() says that the warning chain should be cleared automatically when a new row is read. The client driver does that, but the embedded driver does not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5765) Embedded doesn't clear warnings on
ResultSet when moving to next row
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-5765:
--------------------------------------
Attachment: ClearWarnings.java
The attached program reproduces the bug by executing a statement that returns two rows, with a warning on the first row.
With the client driver it (correctly) prints:
Warnings on row 1: java.sql.SQLWarning: Null values were eliminated from the argument of a column function.
Warnings on row 2: null
With the embedded driver the warning chain isn't cleared before row 2 is read, and it prints:
Warnings on row 1: java.sql.SQLWarning: Null values were eliminated from the argument of a column function.
Warnings on row 2: java.sql.SQLWarning: Null values were eliminated from the argument of a column function.
> Embedded doesn't clear warnings on ResultSet when moving to next row
> --------------------------------------------------------------------
>
> Key: DERBY-5765
> URL: https://issues.apache.org/jira/browse/DERBY-5765
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.2.2
> Reporter: Knut Anders Hatlen
> Attachments: ClearWarnings.java
>
>
> The javadoc for java.sql.ResultSet.getWarnings() says that the warning chain should be cleared automatically when a new row is read. The client driver does that, but the embedded driver does not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5765) Embedded doesn't clear warnings on
ResultSet when moving to next row
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-5765:
-----------------------------------
Urgency: Normal
Bug behavior facts: Deviation from standard,Embedded/Client difference (was: Deviation from standard)
Labels: derby_triage10_10 (was: )
> Embedded doesn't clear warnings on ResultSet when moving to next row
> --------------------------------------------------------------------
>
> Key: DERBY-5765
> URL: https://issues.apache.org/jira/browse/DERBY-5765
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.2.2
> Reporter: Knut Anders Hatlen
> Labels: derby_triage10_10
> Attachments: ClearWarnings.java
>
>
> The javadoc for java.sql.ResultSet.getWarnings() says that the warning chain should be cleared automatically when a new row is read. The client driver does that, but the embedded driver does not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira