RE: [sqlite] Solving the "busy" problem with many reads and a single write

2004-06-15 Thread Wempa, Kristofer \(Kris\), ALABS
>> Our tool to query the database is written in shell and invokes the >> sqlite command. Rather than re-write it in C to go through the API, I >> figured that I'd try changing the read locks to blocking in order to try >> to save time. Reads ONLY happen through this shell tool. Writes only >>

Re: [sqlite] Solving the "busy" problem with many reads and a single write

2004-06-14 Thread D. Richard Hipp
Wempa, Kristofer (Kris), ALABS wrote: > I'm new to this list and I didn't see this question answered in the places I > looked. We have a system that uses a handful of commands to read and write > to an SQLITE database. We already control the commands so that only 1 thread > in one process writes