Thanks for the answers, but I guess I should have made my question more clear. I knew that you can commit every sql statement individually, then the question would be, how can I roll them back?
In other words I'd like something like savepoint and rollback to savepoint, while not loosing the transactions if there is a power failure. I know I can have either one of these, but can I have both!? Josh >> 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! > > Sure. Don't define any transactions. Just issue every command > separately. That way SQLite automatically makes a little transaction > for each command, and once the command is finished it will automatically > COMMIT it. > > Simon. > _______________________________________________ > 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
