Unexpected behavior with commits and rollbacks...

[mtnbiker66]

I guess because I work with Oracle daily and have for 15 years I was expecting to have to explicitly issue a "commit" before it got recorded - I don't have to open a transaction explicitly either. The only way a transaction is committed w/out issuing a "commit" is if I connect to another database with an open transaction.

Every database I know immediately commits a query that is not part of an open transaction. I don't see what's so unexpected here.

---

Added after 4 minutes:

Now that I know I have to issue a db.transaction() I am planning on a single transaction because I need to rollback everything if something fails...

As for the autocommit - because I work in Oracle and I suppose that must be turned off, as I said above I have to issue a commit and rollback for everything...Nothing is automatically committed with either the DB or the software that runs on top of it so I was caught a little off-guard with SQLite's auto commit...


Kodi