Hullo all, Does anyone have solid code examples (in C/C++) or pseudo code of how to establish re-try code/logic successfully?
I have a database (simple schema) with two tables on which I perform "concurrent" udpates over NFS (yes, terrible I know - but it's what we have). Eventually, I get into a dead-locked (I think) situation with a hot journal. Only updates are done. At present we don't have any re- try logic, which is pretty dumb, but we are new to Sqlite3 and erroneously assumed it does the re-try logic on its own. Any pointers will be helpful. I'm starting to think that sqlite3 is not a good fit for our purposes. Large updates, distributed over several cores over NFS - supposedly concurrent "but not really"? Also: What exactly is the difference between BEGIN_IMMEDIATE and BEGIN_EXCLUSIVE? Many thanks, -rosemary. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
