I'd like this clarified too. I specifically don't use transactions when I'm selecting. In fact, I'll select, then start a transaction later for inserting the results. Would I be better off wrapping the whole thing in a transaction?
Wednesday, November 2, 2011, 9:13:20 AM, you wrote: BMI> Maybe my memory is fading but this is the first time I've heard BMI> anybody say the wrapping a BEBIN around a SELECT was needed. I'd BMI> swear it was always said it wasn't ever needed. >>From the docs BMI> http://www.sqlite.org/lang_transaction.html BMI> basically, any SQL command other than BMI> SELECT<http://www.sqlite.org/lang_select.html>) will BMI> automatically start a transaction if one is not already in effect BMI> Now you're saying SELECT always starts a transaction? BMI> Michael D. Black BMI> Senior Scientist BMI> Advanced Analytics Directorate BMI> Advanced GEOINT Solutions Operating Unit BMI> Northrop Grumman Information Systems BMI> _______________________________________________ BMI> sqlite-users mailing list BMI> sqlite-users@sqlite.org BMI> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
