I have completed all the back end development that is using SQLite,
minus on issue:
error handling
I am using SQLite in Axis2/C web services on Windows and later on OSX.
On Windows Apache starts up lots of threads and eventually spawns more
processes, I think in the *NIX world it simply spawns a number of
processes.
I am wondering, to what degree do I really need to concern myself with
error handling? Will SQLite return errors on a regular basis if one
thread or process tries to access the database when another
thread/process already has a lock or will it handle such a situation
normally and only in extreme cases do I need to worry about it, or will
this happen often so I need to check all the time and code things to
take a break and than to retry?
I know I need to look for errors and fail gracefully, I am trying to
figure out to what degree do I need to go? If there is an error, is it
going to be a serious error where it needs to bubble to the user or is
it a minor thing the code should try to fix first?
Sam
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
