[sqlite] Version 3.25.1 coming soon....

2018-09-17 Thread Richard Hipp
Thanks for the bug reports. Two new bugs were added in the 3.25.0 release, so we will shortly have a 3.25.1 release to fix them. A draft change-log for 3.25.1 can be seen here: https://www.sqlite.org/draft/releaselog/3_25_1.html We *really* appreciate your bug reports. But we appreciate

Re: [sqlite] SQLITE touches unchanged expression indexes on update

2018-09-17 Thread Deon Brewis
This seems to work perfectly for expression indexes. Thanks, it makes a HUGE difference for us! Would you perhaps be able to make a similar fix for partial indexes? i.e. this scenario: CREATE TABLE Foo(x, y, z); CREATE INDEX FooX on Foo(x); CREATE INDEX FooZ on Foo(z); CREATE INDEX

Re: [sqlite] [EXTERNAL] Last_row_id

2018-09-17 Thread David Raymond
I can't seem to find where/if it's mentioned, but I believe the only use of a select statement in a trigger is to call the raise function and trigger some level of error. https://www.sqlite.org/lang_createtrigger.html -Original Message- From: sqlite-users

Re: [sqlite] [EXTERNAL] Last_row_id

2018-09-17 Thread Hick Gunter
A trigger program does not return any result rows. -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Yadwindersingh Gesendet: Sonntag, 16. September 2018 03:28 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL]

[sqlite] Building sqlite-autoconf-3250000 with enable-rtree and enable-session

2018-09-17 Thread death lock
I'm building on Debian10 : warning: ISO C99 requires whitespace after the macro name : error: missing binary operator before token "1" sqlite3.c:308:5: note: in expansion of macro ‘SQLITE_ENABLE_RTREE’ * 'space' missing after $BUILD_CFLAGS --- a/configure 2018-09-15 15:36:05.0 +0200

[sqlite] Possible bug in window function queries.

2018-09-17 Thread Shawn Wagner
Been playing around with the new window functions in 3.25, and ran into something that looks like an infinite loop. Working with the t1 table many of the examples in the documentation use, I've come up with a minimal test case: sqlite> select id, b, lead(c, 1) over (order by c) as x from t1

[sqlite] Regression with sqlite 3.25, table renaming and triggers referencing rtree

2018-09-17 Thread Even Rouault
Hi, I just found an issue when a renaming a table when one of its trigger references a column of a rtree echo ' CREATE TABLE "mytable" ( "fid" INTEGER PRIMARY KEY, "geom" BLOB); CREATE VIRTUAL TABLE "rtree_mytable_geom" USING rtree(id, minx, maxx, miny, maxy); CREATE TRIGGER

[sqlite] X64

2018-09-17 Thread Evert van Dijken
Is there no new X64 version? -- With kind regards, Evert van Dijken De Hazelaar 5 6921XA Duiven (NL). --- Deze e-mail is gecontroleerd op virussen door AVG. http://www.avg.com ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] Last_row_id

2018-09-17 Thread Yadwindersingh
Hi all; I am using vs15.x Create trigger return_pono after insert on po Begin Select last_insert_rowid(); End Trigger works quite fine in sqlite but fails to return any value to vb.net statement Dim lrow as int64 Lrow = some_cmd.executescalar() Please help Thank you

Re: [sqlite] [EXTERNAL] The "natural" order of the query results.

2018-09-17 Thread Richard Damon
On 9/17/18 2:19 AM, John Found wrote: > On Mon, 17 Sep 2018 06:02:37 + > Hick Gunter wrote: > >> SQLite handles GROUP BY and ORDER BY in basically the same way. If there is >> an apropirate index, then it will use this index and the rows will be >> returned in visitation order of this

Re: [sqlite] [EXTERNAL] The "natural" order of the query results.

2018-09-17 Thread Graham Holden
In particular, there's a not implausible optimisation opportunity that could alter things... In the general case, the execution of "GROUP BY a, b" will "naturally" involve a sort on "a, b" to bring all the "to be grouped" entries together. In the OP's case, there's a primary key on "a, b" so

Re: [sqlite] [EXTERNAL] The "natural" order of the query results.

2018-09-17 Thread Simon Slavin
On 17 Sep 2018, at 7:19am, John Found wrote: > Yes, of course, but you forgot about INDEXED BY clause. It will force using > particular index. So, the query planner will always use exactly this index, > regardless of how optimal it is and > as long as GROUP BY and ORDER BY are working the same

Re: [sqlite] [EXTERNAL] The "natural" order of the query results.

2018-09-17 Thread John Found
On Mon, 17 Sep 2018 06:02:37 + Hick Gunter wrote: > SQLite handles GROUP BY and ORDER BY in basically the same way. If there is > an apropirate index, then it will use this index and the rows will be > returned in visitation order of this index. If, for exmaple by adding a new > index or

Re: [sqlite] [EXTERNAL] The "natural" order of the query results.

2018-09-17 Thread Hick Gunter
SQLite handles GROUP BY and ORDER BY in basically the same way. If there is an apropirate index, then it will use this index and the rows will be returned in visitation order of this index. If, for exmaple by adding a new index or even an upgrade of the Query Planner, a different execution plan