Hello to all, I've been working on DBMS systems for a couple of years now (namely MS-SQL and MySQL) and I find SQLite's usage of transactions to be quite unique and interesting. I've been reading on different websites about them and one particular site (which sadly I can't remember) confused me a bit. They were recommending that transactions be used even on select statements if they were consecutive. I find this confusing since I thought transactions were only useful if you are making changes and want a mechanism to rollback changes if errors occur. So from what I gather, pseudocode like this should theoretically work correcty:
Start Transaction; Query the database; Do the needed operations on the resultset; Query the database with a different query; Do the needed operations on the resultset; Commit Transaction; My questions are then, 1) is this correct? 2) if no changes are being made to the database, what is being commited? 3) is the 'optimization' coming from preventing SQLite from generating a new transaction for each query? And an off-topic question if I may, is there a way to browse through archives of older mailings? I'd hate to ask questions that have been answered thousands of times. Cheers, -- // -------------------------------------- Enrique Ramirez Irizarry _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
