Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-18 Thread curmudgeon
8 d. Omit unused LEFT JOINs even if they are not the right-most joins of a query. Thanks for fixing this. Working fine for me so far. -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___ sqlite-users mailing list

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-14 Thread J Decker
On Tue, Jan 9, 2018 at 12:30 PM, J Decker wrote: > swarmvtab3 test is still failing... (windows 10, msvc 2017) 10.0.16299.0 > > swarmvtab3-1.2.3... > Error: inconsistent ::dbcache and disk > swarmvtab3-1.3.3... > Error: inconsistent ::dbcache and disk > > This works > > On

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-13 Thread petern
Richard. As you are probably already aware, I forgot about the encoding column. An encoding (UTF8,UTF16,...) column would also needed for the PRAGMA function_list report to be the key for functions differing only by the encoding flag: https://sqlite.org/c3ref/create_function.html One final

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-13 Thread petern
Single builtin functions that otherwise would have required two or more separate create_function calls should have two or more corresponding simulated entries for plain and aggregate flavors distinguishable by column values.max(A) aggregate and max(A,B,...) function could look something like

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-12 Thread Richard Hipp
On 1/12/18, petern wrote: > Is adding arg_count and > is_aggregate columns to PRAGMA function_list() on the roadmap? How would that work with functions like coalesce() and max() that take an arbitrary number of arguments, or like max() that is an aggregate with one

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-12 Thread petern
This is premature of course. The columns of the current PRAGMA function_list() report do not form a practical key for functions. Additional columns arg_count and is_aggregate would be needed join PRAGMA function_list() with a function description table. Suggestion: As an example of both testing

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-12 Thread petern
Ryan. The core and sqlite3_create_function...() needn't be burdened at all except to store some very basic description strings as a compile time option. PRAGMA function_list() cold gather descriptions on the fly by: 1. Spinning through the list of registered %_function_description(F,N)

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-11 Thread R Smith
On 2018/01/11 8:11 PM, petern wrote: With SQLITE_INTROSPECTION_PRAGMAS turned on, is a function description on the roadmap? It would be very helpful to expose a short description of function arguments. Implementation suggestion: a new trailing argument "description" on

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-11 Thread petern
Or, more practically, please consider a virtual style API where PRAGMA function_list() gathers function description strings from all registered 2 argument functions named like %_function_description(F,N) where F is the function name and N is the argument count. A good example implementation might

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-11 Thread petern
With SQLITE_INTROSPECTION_PRAGMAS turned on, is a function description on the roadmap? It would be very helpful to expose a short description of function arguments. Implementation suggestion: a new trailing argument "description" on sqlite3_create_function() or sqlite3_create_function_v2() and

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Gwendal Roué
No more glitch with sqlite3_column_name :-) Thanks Richard, Gwendal > Le 10 janv. 2018 à 02:06, Richard Hipp a écrit : > > All of the minor issues mentioned by prior emails in this thread > should now be fixed. Thanks to everybody for proof-reading and > testing! > > Fresh

[sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Richard Hipp
All of the minor issues mentioned by prior emails in this thread should now be fixed. Thanks to everybody for proof-reading and testing! Fresh source code is now available on trunk (https://sqlite.org/src/info/trunk) and from the "Prerelease Snapshot" link on the https://sqlite.org/download.html

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Richard Hipp
On 1/9/18, E.Pasma wrote: > Dear SQLite developers and eventual PowerPC users, > using a likely outdated compiler: > powerpc-apple-darwin9-gcc-4.0.1 > a compile error occors: > shell.c:10062: error: conflicting types for ‘integerValue’ > shell.c:9169: error:

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread E.Pasma
Dear SQLite developers and eventual PowerPC users, using a likely outdated compiler: powerpc-apple-darwin9-gcc-4.0.1 a compile error occors: shell.c:10062: error: conflicting types for ‘integerValue’ shell.c:9169: error: previous implicit declaration of ‘integerValue’ was here

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread J Decker
On Tue, Jan 9, 2018 at 1:19 PM, Gwendal Roué wrote: > > > Le 9 janv. 2018 à 21:47, Richard Hipp a écrit : > > > > On 1/9/18, Gwendal Roué wrote: > >> 1. For statements made of parameters, such as `SELECT ?, ?` or `SELECT > :a, >

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Gwendal Roué
> Le 9 janv. 2018 à 21:47, Richard Hipp a écrit : > > On 1/9/18, Gwendal Roué wrote: >> 1. For statements made of parameters, such as `SELECT ?, ?` or `SELECT :a, >> :b`, the sqlite3_column_name used to return the parameter name ("?" or ":a" >> etc.)

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Richard Hipp
On 1/9/18, Gwendal Roué wrote: > 1. For statements made of parameters, such as `SELECT ?, ?` or `SELECT :a, > :b`, the sqlite3_column_name used to return the parameter name ("?" or ":a" > etc.) for all parameters, the last one included. The latest version returns > an

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread J Decker
swarmvtab3 test is still failing... (windows 10, msvc 2017) 10.0.16299.0 swarmvtab3-1.2.3... Error: inconsistent ::dbcache and disk swarmvtab3-1.3.3... Error: inconsistent ::dbcache and disk On Tue, Jan 9, 2018 at 11:46 AM, Simon Slavin wrote: > On 9 Jan 2018, at

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Gwendal Roué
Hello, I could spot two behavior changes in f6355970 while testing GRDB.swift. 1. For statements made of parameters, such as `SELECT ?, ?` or `SELECT :a, :b`, the sqlite3_column_name used to return the parameter name ("?" or ":a" etc.) for all parameters, the last one included. The latest

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Simon Slavin
On 9 Jan 2018, at 6:46pm, Richard Hipp wrote: > The latest change summary can be seen at > https://www.sqlite.org/draft/releaselog/3_22_0.html and the draft In … For "clobbering" use "overwriting", if only for the sake of

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread David Raymond
sion of SQLite Database Subject: [sqlite] SQLite 3.22.0 coming soon Version 3.22.0 will probably be released soon. Your help in beta-testing is appreciated. Please download the latest "trunk" sources (from https://sqlite.org/src/info/trunk) or a pre-release snapshot (the top-most li

Re: [sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Donald Griggs
In an attempt to be helpful, two possible typos are: https://www.sqlite.org/draft/cli.html#expert If this option is pass a non-zero argument [change pass -> passed] https://www.sqlite.org/draft/releaselog/3_22_0.html A complex result set bias the decision Maybe " A complex

[sqlite] SQLite 3.22.0 coming soon

2018-01-09 Thread Richard Hipp
Version 3.22.0 will probably be released soon. Your help in beta-testing is appreciated. Please download the latest "trunk" sources (from https://sqlite.org/src/info/trunk) or a pre-release snapshot (the top-most link at https://sqlite.org/download.html) and verify that you are able to build and