Hi all.
 
 I was wondering if the following  design could function:
 
 Create two threads, similiar in vane to test_server.c...
 Except one is a reading thread and one is for writing. 
 The client code would start a transaction for writing (ie BEGIN txn) then its 
requests would be enqued to the writer thread... (along with any selects that 
it may perform).
 
 Similarly all other statements  from other threads (ie selects) would go to 
the reader thread.
 
 Would the reader be blocked by the writer? Would the writer be blocked by the 
reader?
 
 I guess  I'm unclear what I can/cant do using sqlite and how to gain as much 
performance as possible.  (obviously transactions work very well, which I'm 
already doing).
 
 thanks,
 Ken
 
 
 

Reply via email to