SQLite does not use row level locking, only file level locking. You can use BEGIN IMMEDIATE to exclude writers or BEGIN EXCLUSIVE to exclude readers and writers. If you do not explicitly start a transaction, each statement constitutes it's own transaction.
-----Ursprüngliche Nachricht----- Von: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Scott Doctor Gesendet: Dienstag, 24. Mai 2016 19:34 An: sqlite-users@mailinglists.sqlite.org Betreff: [sqlite] SELECT ... FOR UPDATE My current project has me bouncing between sqlite and mysql. In mysql, to lock a row of data at the start of a process to hold off concurrent operations, the recommended technique with the innodb engine is to issue SELECT field FROM table FOR UPDATE; This holds off any other process from accessing that row until it is released. This is according to the mysql manual. My question is, looking through the sqlite documentation, it is not clear how sqlite will handle that statement. Since I am porting sql between several databases, I am trying to figure out if I need to search and destroy any of those statements from mysql when converting it to sqlite. ------------ Scott Doctor sc...@scottdoctor.com ------------------ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: h...@scigames.at This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
