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
