[jira] Commented: (DERBY-1654) Calling Connection.commit() does not throw exception in autocommit mode

["Kathey Marsden (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426932 ] 
            
Kathey Marsden commented on DERBY-1654:
---------------------------------------

We might need to be careful with regard to existing appication impact on this one.  Is anyone planning on fixing this for 10.2?   I think I would prefer to see an announcement now that we plan to fix this for 10.3 and defer it to the next release.  I'd recommend DERBY-790 instead to anyone  looking for a low hanging fruit JDBC compliance issue #:)





> 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: 10.1.3.1
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         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