Is this still true? As in, do I only need to use a mutex for write operations that might come from multiple threads, but not read? What about a read and write happening simultaneously from two different threads?
On Tuesday, March 4, 2008 12:32:36 AM UTC-5, Tzury Bar Yochay wrote: > > > > did you post this code? > at http://tzury.jottit.com/sqlite-threadsafe-writer I put a different > version (no tcp daemon but a thread) > > > What happens if you try to do a db write > > from several web.py threads and you don't have a scheme like yours? > > Does it corrupt the db? Give an error? Lock until each write is done? > > With SQLite 3, If you try to write from to sqlite while another one is > writing you get an error. I did not experienced any corruption. > > >Does the web.py database API solve these problems? > The reason I wrote that one was errors I got using the simple > approach. > > > -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy. For more options, visit https://groups.google.com/groups/opt_out.
