Re: [sqlite] Understanding the WITH clause

On 15-6-2019 18:24, Sam Carleton wrote: Pax vobiscum, Sam Carleton I had to pull up a dictionary to know what Pax (=Peace) you are talking about.. (https://en.wikipedia.org/wiki/Pax_(liturgy)) "In Christian liturgy

Re: [sqlite] SQLITE_MAX_COLUMN should be a runtime knob for Machine Learning

On 15 Jun 2019, at 2:42pm, Dan Kaminsky wrote: [about the 32676 hard limit on the number of columns in a table] > I spent quite a bit of time hacking large column support into a working > Python pipeline, and I'd prefer never to run that in production. > Converting this compile time variable

[sqlite] Understanding the WITH clause

I am working with a nested set tree and reading through Joe Celko's trees and hierarchies in sql source book to refresh the old brain. In section 4.7.1 of the book he has an example that uses a do while statement. It looks like this concept can be implemented in SQLite by using the WITH clause,

[sqlite] SQLITE_MAX_COLUMN should be a runtime knob for Machine Learning

Sqlite3 has something of a normative declaration in its source code: * ** This is the maximum number of ** *** Columns in a table *** Columns in an index *** Columns in a view *** Terms in the SET clause of an UPDATE statement *** Terms in the result set of a SELECT statement

Re: [sqlite] Understanding the WITH clause

I have kept reading and the next section of the book does away with the update and simply creates a recursive function. The goal of the function is to determine the 'weight' of a part by adding up all the subassemblies * qty. At first I thought this might be easier to convert into SQLite, but

[sqlite] pointer-passing interface, and testing if pointer is correct 'type'....

Folks; I have a v-table using the pointer-passing interface, and binding 'null' is a valid use-case. However, to wit there is no way to tell on the v-table implementation side if the sqlite3_value_pointer() returns 'null' because that is what the user explicitly and validly chose, or because

[sqlite] Understanding the WITH clause

I am working with a nested set tree and reading through Joe Celko's trees and hierarchies in sql source book to refresh the old brain. In section 4.7.1 of the book he has an example that uses a do while statement. It looks like this concept can be implemented in SQLite by using the WITH clause,

Re: [sqlite] demoRead() function in test_demovfs.c not consistent with documentation

On 15/6/62 20:08, Dominique Pellé wrote: Hi SQLite page https://sqlite.org/c3ref/io_methods.html says at the bottom: === BEGIN QUOTE === If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill in the unread portions of the buffer with zeros. A VFS that fails to zero-fill short reads

[sqlite] demoRead() function in test_demovfs.c not consistent with documentation

Hi SQLite page https://sqlite.org/c3ref/io_methods.html says at the bottom: === BEGIN QUOTE === If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill in the unread portions of the buffer with zeros. A VFS that fails to zero-fill short reads might seem to work. However, failure to

Re: [sqlite] select within transaction

Thank you, Adrian. I think this is reason changes() exist. Roman Sent from my T-Mobile 4G LTE Device Original message From: Adrian Ho Date: 6/15/19 12:25 AM (GMT-05:00) To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] select within transaction On 15/6/19

Re: [sqlite] Should SQLite distinguish between +0.0 and -0.0 on output?

Maybe the core pb under the question asked here is this prior question : from the standard, is it possible to consider 0.0 as an imprecise representation of 0 ? (if yes, signing 0.0 seems logical to me) Regards, -jm --- L'absence de virus dans ce courrier électronique a été vérifiée par

Re: [sqlite] json path escaping with double quote

Ok, I tried to patch this line: diff --git a/ext/misc/json1.c b/ext/misc/json1.c index d99d360b2..0bb4e1cee 100644 --- a/ext/misc/json1.c +++ b/ext/misc/json1.c @@ -1123,7 +1123,7 @@ static JsonNode *jsonLookupStep( u32 iStart, iLabel; JsonNode *pNode; iStart =

Re: [sqlite] Should SQLite distinguish between +0.0 and -0.0 on output?

On 2019-06-12 6:35 a.m., Richard Hipp wrote: IEEE754 floating point numbers have separate representations for +0.0 and -0.0. As currently implemented, SQLite always display both quantities as just "0.0". Question: Should SQLite be enhanced to show -0.0 as "-0.0"? Or, would that create