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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/07/17 03:26:48 UTC

[jira] [Updated] (DERBY-3851) Client and embedded differ on sending StatementEvent on Connection.close()

     [ https://issues.apache.org/jira/browse/DERBY-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-3851:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
    
> Client and embedded differ on sending StatementEvent on Connection.close()
> --------------------------------------------------------------------------
>
>                 Key: DERBY-3851
>                 URL: https://issues.apache.org/jira/browse/DERBY-3851
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.5.1.1
>         Environment: JDBC 4.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_11
>
> When a connection is closed, the client driver sends a StatementEvent to all StatementEventListeners registered on the connection being closed. The embedded driver does not send StatementEvents when a connection is closed. Examples can be found in jdbc4/StatementEventsTest. Look for code that calls usingEmbedded() and usingDerbyNetClient() in that class.
> Embedded and client should match if possible, per DERBY-310.

--
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