sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Nick
>Sent: Tuesday, 6 February, 2018 19:25
>To: sqlite-users@mailinglists.sqlite.org
>Subject: Re: [sqlite] [EXTERNAL] Question about threadsafe
>
>Yep, Hick. We have the same understanding.
>But all I found is
Yes. But
Process A begin
Process A insert
Process B begin
Process B insert
Process A end
Process B end
In fact, begin means "BEGIN" and end means "COMMIT".
So I think the result is strange.
And I guess the difference between Serilaized and Multithread
they are always serializing.
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Nick
Gesendet: Mittwoch, 07. Februar 2018 03:25
An: sqlite-users@mailinglists.sqlite.org
Betreff: Re: [sqlite] [EXTERNAL] Question about threadsafe
Yep, Hick. We have the same understanding.
But all I found is that process B did not wait for the lock and began to run
directly.
--
Sent from: http://sqlite.1065341.n5.nabble.com/
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
More than one concurrent writer is not supported. WAL mode only allows readers
to see the state of the db as it was at the start of their transaction while
writers' changes are written to the WAL file.
Threadsafe refers to the interoperation of multiple threads within a single
process. Single
5 matches
Mail list logo