I find sqlite3 as the perfect choice for our embedded application - if it 
hasn't been for the
issues concering concurrency.
My questions are; 
  1.  is the "default behaviour" from sqlite3 to simply ignore inserts if
    the concurrency gets to high? 
2. is there anything (C API) I can do to at least know that it does not do 
an actual insert?
    (tried calling sqlite3_changes() but even that remains silent about 
its results)

Thanks !
Tore
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to