> Hmm... unless read_uncommited is persistant somehow; looks like if I
> just don't try to use shared cache it works... I thought I had
> disabled cache before alone and still got the same results...

read_uncommitted works only when shared_cache is on.

To answer your original question: if you disable shared cache, start
reading transaction on one connection and start writing transaction on
the other connection then you'll be able to read on the first
connection database in the state it was before writing transaction.
But if your writing transaction will grow too big then it won't be
able to proceed until reading transaction is finished.


Pavel


On Sun, Jun 12, 2011 at 4:11 PM, J Decker <d3c...@gmail.com> wrote:
> If I disable enable_shared_cache then there is a pragme
> read_uncommitted that doesn't generate the locks; so non shared,
> read_uncommited combination works;
>
> I tried 'PRAGMA journal_mode=WAL'  which says it returns a string; I
> assume that if I treat it as a query and sqlite3_step I should get
> back this string?  sqlite3_step returns SQLITE_DONE not SQLITE_ROW so
> it looks like there is no data.  I'm currently using version 3.7.5
> amalgamation compiled with vs2010.  updated to 3.7.6.3 and still get
> no result from the pramga.
>
> Hmm... unless read_uncommited is persistant somehow; looks like if I
> just don't try to use shared cache it works... I thought I had
> disabled cache before alone and still got the same results...
>
>
>
> On Sun, Jun 12, 2011 at 5:48 AM, Florian Weimer <f...@deneb.enyo.de> wrote:
>> * J. Decker:
>>
>>> I have enabled sqlite3_enable_shared_cache( 1 );
>>> I have basically two connections to the same database in the same
>>> process.  One connection is used for selects, the other is used for
>>> insert and replace.  I can end up with several threads with selects,
>>> but the writer is only used in by a single thread[at a time].
>>
>> The question seems to belong to the sqlite-users list; Reply-To set.
>>
>> Have you tried using WAL mode?
>> _______________________________________________
>> sqlite-dev mailing list
>> sqlite-...@sqlite.org
>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-dev
>>
> _______________________________________________
> sqlite-dev mailing list
> sqlite-...@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-dev
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to