uesday, 24 July, 2018 11:22
>To: sqlite-users@mailinglists.sqlite.org
>Subject: [sqlite] Immediate mode transaction gets error 5,
>SQLITE_BUSY when attempting commit
>
>Hello. Long time reader, first time poster here.
>
>I have read the pertinent documentation on this issue
glists.sqlite.org
Subject: [sqlite] Immediate mode transaction gets error 5, SQLITE_BUSY when
attempting commit
Hello. Long time reader, first time poster here.
I have read the pertinent documentation on this issue but may have
missed some important point. I am puzzled by some results I am seeing.
A
On 7/24/18, Andy Dickson wrote:
>
> Using sqlite version 3.7.17 (which I know is old but I in my little cube
> have no power to change that).
>
Recent versions of SQLite consume substantially fewer CPU resources
than 3.7.17. See the graph at https://www.sqlite.org/cpu.html
--
D. Richard Hipp
On 24 Jul 2018, at 6:22pm, Andy Dickson wrote:
> I have a database with one process (in one thread) writing to it, and another
> process (also in a single thread) reading from it only.
Do these two processes each have their own connection to the database ?
> The read-only process has
Hello. Long time reader, first time poster here.
I have read the pertinent documentation on this issue but may have
missed some important point. I am puzzled by some results I am seeing.
Apologies in advance for not providing a small code sample that
reproduces the issue, but I think the
5 matches
Mail list logo
