of Brad House [b...@monetra.com]
Sent: Tuesday, May 01, 2012 8:22 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] SQLite 3.7.11 behavioral change from 3.7.10 with
concurrency -- bug?? -- test case!
I agree that the docs for shared-cache mode need to be updated to reflect
On 04/28/2012 09:36 AM, Richard Hipp wrote:
On Sat, Apr 28, 2012 at 8:24 AM, Black, Michael (IS)
> To: General Discussion of SQLite Database
> Subject: EXT :Re: [sqlite] SQLite 3.7.11 behavioral change from 3.7.10
> with concurrency -- bug?? -- test case!
>
> On Fri, Apr 27, 2012 at 6:45 PM, Pavel Ivanov <paiva...@gmail.com> wrote:
>
> > > If two database conn
e Database
Subject: EXT :Re: [sqlite] SQLite 3.7.11 behavioral change from 3.7.10 with
concurrency -- bug?? -- test case!
On Fri, Apr 27, 2012 at 6:45 PM, Pavel Ivanov <paiva...@gmail.com> wrote:
> > If two database connections share the same cache, and one connection
> r
On Fri, Apr 27, 2012 at 7:04 PM, Richard Hipp wrote:
> On Fri, Apr 27, 2012 at 6:45 PM, Pavel Ivanov wrote:
>> > If two database connections share the same cache, and one connection
>> rolls
>> > back, that means it will be changing cache content out from
On Fri, Apr 27, 2012 at 6:45 PM, Pavel Ivanov wrote:
> > If two database connections share the same cache, and one connection
> rolls
> > back, that means it will be changing cache content out from under the
> other
> > database connection, so any queries ongoing in the other
> The insert finishes before the select finishes, but the new row does not
> show up
> in the select either (not that I'm sure if it should or not, I guess that
> might
> be a dirty read). I'm not really sure if this is fully intended behavior or
> not ...
That's indeed an intended behavior for
> If two database connections share the same cache, and one connection rolls
> back, that means it will be changing cache content out from under the other
> database connection, so any queries ongoing in the other connection have to
> abort.
Richard,
Could you please explain this? I understand
On 04/27/2012 04:38 PM, Richard Hipp wrote:
Disable shared cache mode and you should be good to go.
If two database connections share the same cache, and one connection rolls
back, that means it will be changing cache content out from under the other
database connection, so any queries ongoing
On Fri, Apr 27, 2012 at 3:50 PM, Brad House wrote:
> On 04/27/2012 02:00 PM, Brad House wrote:
>
>>
>> Only the connection that does the rollback has its queries aborted.
>>>
>>
>> That is not the behavior I am seeing in 3.7.11, but was the behavior
>> I saw in 3.7.10.
>>
>>
Ok, I guess attachments don't come through.
I've uploaded it here:
http://www.brad-house.com/other/sqlite_test.c
-Brad
On 04/27/2012 03:50 PM, Brad House wrote:
On 04/27/2012 02:00 PM, Brad House wrote:
Only the connection that does the rollback has its queries aborted.
That is not the
On Fri, Apr 27, 2012 at 3:50 PM, Brad House wrote:
>
>
> As promised, I've attached a test case which uses the SQLITE amalgamation.
>
The mailing list strips attachments. Send us a link, instead.
--
D. Richard Hipp
d...@sqlite.org
On 04/27/2012 02:00 PM, Brad House wrote:
Only the connection that does the rollback has its queries aborted.
That is not the behavior I am seeing in 3.7.11, but was the behavior
I saw in 3.7.10.
If you are seeing other connections get queries aborted, that is something
new that I have not
13 matches
Mail list logo