Yes, It is my fault. Thanks!
Kristian Waagan-4 wrote: > > Hi, > > I think this is expected behavior, because you don't close the statement. > From [1] (* added by me): > "Auto-commit mode means that when a statement is completed, the method > /commit/ is called on that statement automatically. Auto-commit in > effect makes every SQL statement a transaction. The commit occurs when > the statement completes or the next statement is executed, whichever > comes first. *In the case of a statement returning a /ResultSet/, the > statement completes when the last row of the /ResultSet/ has been > retrieved or the /ResultSet/ has been closed explicitly.*" > > When you call close Connection.close(), Derby will do a rollback because > there is an active transaction (if you had auto-commit set to false, an > exception would have been thrown). > > > Hope this helps, > -- > Kristian > > [1] http://db.apache.org/derby/docs/dev/devguide/cdevconcepts29416.html > > -- View this message in context: http://old.nabble.com/Why-derby-do-not-auto-commit--tp28726531p28727742.html Sent from the Apache Derby Developers mailing list archive at Nabble.com.
