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] Commented: (DERBY-1654) Calling Connection.commit() does not throw exception in autocommit mode
Date Wed, 09 Aug 2006 14:51:16 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426936 ] 
Dyre Tjeldvoll commented on DERBY-1654:

Somehow I expected that you would say just that :) If you look closely you will see that the
issue was created with "Fix Version" 10.3.

> Calling Connection.commit() does not throw exception in autocommit mode
> -----------------------------------------------------------------------
>                 Key: DERBY-1654
>                 URL: http://issues.apache.org/jira/browse/DERBY-1654
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>             Fix For:
>         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.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message