Hi gurus,

I'm aware of the limitations that generally preclude using SQLite over 
a network.
Anyway do you think that doing so with every read or write operation 
wrapped inside an explicit exclusive transaction can be a safe way to 
run a DB for a group of 10 people under low load (typically 2Kb read or 
100b writes per user per minute)?
Schema will be very simple and queries / inserts as well.  Speed is not 
a real concern.

So do you believe DB corruption can still occur in this context, 
knowing that the use will be for a very limited time (2-3 weeks) and 
low volume (~50K rows)?

Using one of the available client/server wrappers is not a suitable option.
This is targeted at Windows, XP or later.

Do you have a better idea to make the thing more robust, even at 
additional cost in concurrency and/or speed.

_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to