Keith,
For normal operations the writer will wait until the reading is done. But
I have a client that is remote and is very slow and could sit on a select
statement indefinitly. In this case I would need to create a temp table.
Thanks,
-Alex
On Mon, Jun 2, 2008 at 11:53 AM, Keith Goodman <[E
On Mon, Jun 2, 2008 at 8:12 AM, Alex Katebi <[EMAIL PROTECTED]> wrote:
> Hi Keith,
>
> Your observation is correct. I did not know that when selecting a table a
> shared lock is aquired by the reader and writes are locked out until the
> last row is read or stmt is finialized. This is true even f
Hi Keith,
Your observation is correct. I did not know that when selecting a table a
shared lock is aquired by the reader and writes are locked out until the
last row is read or stmt is finialized. This is true even for in-memory
database.
One cure for this problem is to create a temorary ta
On Sun, Jun 1, 2008 at 2:19 PM, Alex Katebi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I have a in-memory database with some tables. Each table has a single
> record writer and multiple readers.
> Readers and writes prepare their own sqlite3_stmt for the db. Everyone
> operates within a single thre
Hi All,
I have a in-memory database with some tables. Each table has a single
record writer and multiple readers.
Readers and writes prepare their own sqlite3_stmt for the db. Everyone
operates within a single thread.
What happens if a reader wants to read a record that has been deleted by the
5 matches
Mail list logo
