Re: [sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-26 Thread Dimitris Bil
ach thread. From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> on behalf of Hick Gunter <h...@scigames.at> Sent: Monday, July 24, 2017 9:05 AM To: 'SQLite mailing list' Subject: Re: [sqlite] Concurrent reads for VTs with in-memory data structures We are using a shared m

Re: [sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-24 Thread Hick Gunter
Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Dimitris Bil Gesendet: Montag, 03. Juli 2017 19:14 An: sqlite-users@mailinglists.sqlite.org Betreff: [sqlite] Concurrent reads for VTs with in-memory data structures I have some virtual tables

Re: [sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-09 Thread Keith Medcalf
; From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of Dimitris Bil > Sent: Tuesday, 4 July, 2017 09:19 > To: SQLite mailing list > Subject: Re: [sqlite] Concurrent reads for VTs with in-memory data > structures > > Keith, thanks for y

Re: [sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-04 Thread Dimitris Bil
mailing list Subject: Re: [sqlite] Concurrent reads for VTs with in-memory data structures If it is singleton data the I suppose you could keep a static pointer to the data structure, a static "use" counter, and a static mutex. Then, for each connection (xConnect), lock the mutex, if

Re: [sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-03 Thread Keith Medcalf
linglists.sqlite.org] > On Behalf Of Dimitris Bil > Sent: Monday, 3 July, 2017 11:14 > To: sqlite-users@mailinglists.sqlite.org > Subject: [sqlite] Concurrent reads for VTs with in-memory data structures > > I have some virtual tables that keep in-memory data structures. Data &

[sqlite] Concurrent reads for VTs with in-memory data structures

2017-07-03 Thread Dimitris Bil
I have some virtual tables that keep in-memory data structures. Data loading is happening at table creation (xCreate and xConnect are the same) and after that, during querying, only read access is needed. Queries do not access any other tables. Is there a way to achieve concurrent execution