> > > MySql works like you described.. Frankly im surprised Postgres doesn't . > > Id imagine there must be a "continue trnasaction" command or something. > > You can define a 'savepoint' inside a transaction. If something goes > wrong you roll back to the savepoint and continue from there. > > You basically roll back to a known-good point. Sqlite implicitly rolls > back to the state that existed before a problematic statement.
Uh.... Then how do they define a transaction? It seems like that's what a transaction is for.
