db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1654) Calling Connection.commit() does not throw exception in autocommit mode
Date Wed, 19 Mar 2008 15:38:24 GMT

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

Dyre Tjeldvoll closed DERBY-1654.

    Resolution: Won't Fix

The issue with existing applications and usability undesirable to fix this.

> Calling Connection.commit() does not throw exception in autocommit mode
> -----------------------------------------------------------------------
>                 Key: DERBY-1654
>                 URL: https://issues.apache.org/jira/browse/DERBY-1654
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>         Attachments: simple.java
> The jdbc spec (don't know chapter and verse) states that an attempt to call Connection.commit()
when Connection.getAutoCommit() is true, must throw an exception. The attached repro (simple.java)
runs fine with Derby (and Postgres), but fails with MySQL:
> dt136804@khepri29~/java$ java -cp $CLASSPATH:. simple com.mysql.jdbc.Driver 'jdbc:mysql://localhost/joindb'
joinuser joinpass foo4
> java.sql.SQLException: Can't call commit when autocommit=true
>         at com.mysql.jdbc.Connection.commit(Connection.java:2161)
>         at simple.main(simple.java:17)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message