On 2011-06-05 12:26, Dagdamor wrote: > If you need a non-transactional (atomic)...
> If you need transactions (although in most of the web cases you don't need > them)... Non-transactional is by definition not atomic. With the single exception of something that is strictly read-only, I have never, ever, seen any database application that did not need transactions. Ever. There's more to transactions than just grouping together multiple SQL statements. If you do any INSERTs, UPDATEs, or DELETEs at all, you need transactions, even if there are no indexes involved, even if the individual statements don't affect each other. Even a simple insert can involve multiple operations like requesting more disk space from the OS, rearranging pointers in the database file on the disk, etc. What happens if there's a power failure while it's in the middle of that insert? With transactions, it gets rolled back when things start up again. Without, you could wind up with a corrupted database. Joe D _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
