Re: [sqlite] Row locking sqlite3

See also http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/2017-August/074060.html - this branch has been around for a while and I think it was mentioned elsewhere that it definitely is being considered for mainline inclusion at some not immediate point. Wout. On Tue, Mar 26,

Re: [sqlite] JSON1: queries on object keys

> On Mar 26, 2019, at 10:41 AM, Warren Young wrote: > > The biggest problem with these isn’t the use of JSON per se, it’s that each > one is unindexed, so they’ll all be a full table scan. Well, we don’t know that; the question was just about whether those are reasonable queries, not

Re: [sqlite] CASE optimization opportunity (was: filling a key/value table)

See if something like this works better: INSERT INTO logidx(keyid,value,location) SELECT id, val, location from ( SELECT k.id id, (case k.name when 'type' then l.type when 'name' then l.name when 'size' then l.size else NULL end) AS val, l.location location FROM logfile l, logkey k )

[sqlite] unsubscribe failed

I submitted an unsubscribe request. I received the below message in my Spam folder. I did not receive instructions on how to complete the unsubscribe action. This is the mail system at host sqlite.org. I'm sorry to have to inform you that your message could not be delivered to one or more

Re: [sqlite] JSON1: queries on object keys

On Mar 26, 2019, at 8:35 AM, Wout Mertens wrote: > > what would be the best way to answer these, given `CREATE TABLE foo(id > TEXT, json JSON);` and json is always a json object: > > - all rows with a given key bar > - SELECT * FROM foo WHERE json_extract(json, '$.bar') IS NOT NULL; >

Re: [sqlite] Row locking sqlite3

I’ve seen the server mode branch, but to me it’s a deal-breaker that it requires SYNCHRONOUS = OFF. This BEGIN CONCURRENT idea really interests me. By using WAL mode,

Re: [sqlite] read-only database in WAL mode and temporary files

From my understanding, the SHM file is needed to communicate to writers that they are in fact performing a read operation (i.e., locks). Without that communication, a writer might insert some data and then perform a checkpoint, without knowing that there is a database reader, and thus overwrite

Re: [sqlite] JSON1: queries on object keys

On Tue, Mar 26, 2019 at 3:35 PM Wout Mertens wrote: > Hi amazing list, > > what would be the best way to answer these, given `CREATE TABLE foo(id > TEXT, json JSON);` and json is always a json object: > >- all rows with a given key bar > - SELECT * FROM foo WHERE json_extract(json,

[sqlite] JSON1: queries on object keys

Hi amazing list, what would be the best way to answer these, given `CREATE TABLE foo(id TEXT, json JSON);` and json is always a json object: - all rows with a given key bar - SELECT * FROM foo WHERE json_extract(json, '$.bar') IS NOT NULL; - all rows where there are only any of the

[sqlite] CASE optimization opportunity (was: filling a key/value table)

This works as expected, thanks. SQLite implements this as a pair of coroutines: Routine A) does a nested scan of the logfile (outer loop = just read the logifle once) and the logkey table (inner loop) Routine B) does the actual insert(s) into the logidx table Unfortunately, the necessary

Re: [sqlite] sqlar: makeDirectory called with permission bits of file

Hi Richard, Dominique, I downloaded and compiled the latest trunk and can confirm that it fixes this issue. Thanks! Martin > -Ursprüngliche Nachricht- > Von: sqlite-users Im Auftrag > von Dominique Devienne > Gesendet: Dienstag, 26. März 2019 11:57 > An: SQLite mailing list >

Re: [sqlite] proposal: make the archive option -Au to update only newer files. /Patch included/

On Mon, Mar 25, 2019 at 8:35 AM Захар Малиновский < zakhar.malinovs...@gmail.com> wrote: > I would like to know is there a way to see if this proposal rejected or > something? Is this a write ML to propose with patch? > Looks like Richard implemented what you need?

Re: [sqlite] sqlar: makeDirectory called with permission bits of file

On Mon, Mar 25, 2019 at 4:07 PM Richard Hipp wrote: > Please try the latest trunk check-in and let use know whether or not it > fixes your issue. > For reference: https://www.sqlite.org/src/info/f11c89595dc65f89 ___ sqlite-users mailing list