autocommit - turning on after transaction is committed?

[Toby Davis]

When I turn off autocommit to perform transactions (such as two stored procedure calls involving inserts), is it necessary that I set autocommit(true) after committing?
Example code (using Sun's example, which is close to mine):

con.setAutoCommit(false);
PreparedStatement updateSales = con.prepareStatement(
    "UPDATE COFFEES SET SALES = ? WHERE COF_NAME LIKE ?");
updateSales.setInt(1, 50);
updateSales.setString(2, "Colombian");
updateSales.executeUpdate();
PreparedStatement updateTotal = con.prepareStatement(
    "UPDATE COFFEES SET TOTAL = TOTAL + ? WHERE COF_NAME LIKE ?");
updateTotal.setInt(1, 50);
updateTotal.setString(2, "Colombian");
updateTotal.executeUpdate();
con.commit();  // committed
con.setAutoCommit(true);  // is this necessary

Why do I need to set the connection's autocommit back to true at the end? I was advised to do this, but logically, I've already committed the transaction... and have no need for autocommit in my apps.
(Note the connection is from a pooled Datasource)
Thanks
--

[Mahesh Mamani]

Hello,
I do agree that the statement used at the end is not required, but u may make Ur code a bit smarter thur' this:
try {
if (!con.getAutoCommit()) {
con.setAutoCommit(true);
}
}
catch (DBException dbe) {}
Try it n let me know

MSM

[Adam Hardy]

It doesn't make any difference to the transaction that you have just committed, but it would make a difference to later bits of code using the same connection.
If you're using a connection pool, that's more true.
You might have a piece of code afterwards that doesn't want a transaction and doesn't bother checking that autocommit is true and so never does a commit.

[Toby Davis]

Got it, thanks for the replies. I have transaction off for all my calls so far - but you never know.
---