Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Clemens Ladisch
Petite Abeille wrote: > Oh! Row Values! Nice! :) This description exchanges "LHS" and "RHS". Regards, Clemens ___ sqlite-users mailing list

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Dominique Devienne
On Thu, Sep 22, 2016 at 9:04 PM, Richard Hipp wrote: > Our current schedule for the next SQLite release (3.15.0) is for > 2016-10-14. > [...] you can review the change log > (https://www.sqlite.org/draft/releaselog/3_15_0.html). > SQLite Release 3.15.0 (Pending) > > Added

Re: [sqlite] Strange problem (pehaps bug) with sqlite + json

2016-09-23 Thread Gilles Vollant
With sqlite.exe from tools zipfile, I reproduce the bug with this script: If I add, just after the create table the line create index if not exists idxtype on records(activitytype); I have a correct result If I don't add the index, I've "malformed json" error. Can you try reproduce?

Re: [sqlite] Strange problem (pehaps bug) with sqlite + json

2016-09-23 Thread Dan Kennedy
On 09/23/2016 03:09 PM, Gilles Vollant wrote: With sqlite.exe from tools zipfile, I reproduce the bug with this script: If I add, just after the create table the line create index if not exists idxtype on records(activitytype); I have a correct result If I don't add the index, I've

Re: [sqlite] Strange problem (pehaps bug) with sqlite + json

2016-09-23 Thread Dominique Devienne
On Fri, Sep 23, 2016 at 11:58 AM, Hick Gunter wrote: > SQLite evaluates the WHERE clause from left to right, which means it needs > to evaluate xyz and thereby call json_extract first, even before it can > determine that no rows match the second condition. > > Maybe the

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread R Smith
On 2016/09/22 9:04 PM, Richard Hipp wrote: Our current schedule for the next SQLite release (3.15.0) is for 2016-10-14. 2.2. Row Values In UPDATE Statements Row values can also be used in the SET clause of an UPDATE statement. The RHS

Re: [sqlite] Strange problem (pehaps bug) with sqlite + json

2016-09-23 Thread Hick Gunter
SQLite evaluates the WHERE clause from left to right, which means it needs to evaluate xyz and thereby call json_extract first, even before it can determine that no rows match the second condition. Maybe the transformation algorithm can be changed to check the "subselect constraints" first?

[sqlite] Table alias for FTS5

2016-09-23 Thread Alexei Gilchrist
Hi, I’ve just come across an oddity using FTS5. I have an FTS table that may get joined multiple times in a query so each time I give it an alias. The problem is that the match operator generates a “no such column” error when I use the table alias. e.g. SELECT DISTINCT n.uid FROM nodes n

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Richard Hipp
On 9/23/16, Dominique Devienne wrote: > > For a long time, I've wanted to bind the RHS of a IN operator of arbitrary > size, See the carray() table-valued function extension: https://www.sqlite.org/draft/carray.html -- D. Richard Hipp d...@sqlite.org

Re: [sqlite] Table alias for FTS5

2016-09-23 Thread Richard Hipp
On 9/23/16, Alexei Gilchrist wrote: > Hi, > > I’ve just come across an oddity using FTS5. I have an FTS table that > may get joined multiple times in a query so each time I give it an > alias. The problem is that the match operator generates a “no such > column” error when I use

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Dominique Devienne
On Fri, Sep 23, 2016 at 1:39 PM, Richard Hipp wrote: > On 9/23/16, Dominique Devienne wrote: > > > > For a long time, I've wanted to bind the RHS of a IN operator of > arbitrary size, > > See the carray() table-valued function extension: >

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Dominique Devienne
On Fri, Sep 23, 2016 at 5:04 PM, Keith Medcalf wrote: > [...] bind the RHS of a IN operator of arbitrary size [...] > > A carray won't work for you? No. carray doesn't support blobs. The semantic of carray is fundamentally flawed for variable-sized values. And the

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Keith Medcalf
> For a long time, I've wanted to bind the RHS of a IN operator of arbitrary > size, > instead of > 1) having to hard-code the cardinality, e.g. IN (:1, :2); > 2) or use a tmp table to insert the values and use a subquery; > 3) somehow use an eponymous vtable as the RHS. > > None of which is

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread David Raymond
-Add the ".testcase" and ".check" dot-commands. Is there documention on what these are? I don't see anything on them in the linked CLI page draft. https://www.sqlite.org/draft/cli.html -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Quan Yong Zhai
http://sqlite.org/draft/rowvalue.html Quote<< A "row value" is an ordered list of two or more scalar values. In other words, a "row value" is a vector.>> some word in the above sentence not strictly correct. A “row value” is a tuple, not a vector. When your using a tuple, you know how many

Re: [sqlite] SQLite 3.15.0 scheduled for 2016-10-14

2016-09-23 Thread Gerry Snyder
Just curious--will Tcl lists be usable as row values? Gerry Snyder On Thu, Sep 22, 2016 at 12:04 PM, Richard Hipp wrote: > Our current schedule for the next SQLite release (3.15.0) is for > 2016-10-14. > > Your beta-tests are appreciated. You can get a pre-release snapshot >