> Is there any way to have them committed by > default? Basically I *only* want the transaction rolled back in case of an > explicit rollback statement, not due to program crash/power failure, etc. Does > anyone know of a way of doing this?
You can avoid transaction begin/commit statements, so that every statement is in its own transaction and automatically committed at the end of execution. Otherwise if program crashes there's no way to know what non-corrupted state should database be in while transaction is not fully committed yet. Pavel On Mon, Aug 9, 2010 at 12:05 PM, Josh <jnf...@grauman.com> wrote: > Hello all, > > I'm new to the list and had a question. I know the default behavior for > savepoints (or any transactions) is that if they have not been committed, if > the program crashes, they are lost. Is there any way to have them committed by > default? Basically I *only* want the transaction rolled back in case of an > explicit rollback statement, not due to program crash/power failure, etc. Does > anyone know of a way of doing this? Thanks! > > Josh > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
