Re: [sqlite] [EXTERNAL] Query on TEMP view.

HAVING is only applicable to GROUP BY's. That is, the WHERE clauses constrain what goes into the sorter for the "group by" operation and the HAVING clauses constrain what comes out of the sorter from the "group by" operation and is returned as a query result. I think that the issue is that th

Re: [sqlite] [EXTERNAL] Query on TEMP view.

In the sqlite shell, enter the .explain command and then EXPLAIN QUERY PLAN for an explanation of the plan, and EXPLAIN for the generated bytecode. This usually helps to understand what sqlite is thinking (although maybe not why). Note that WHERE constraints are applied to the input set whe

Re: [sqlite] Query on TEMP view.

There are a myriad of reasons for the behaviour you are seeing and they affect only performance and not correctness. In other words, you think that your UDF is more "expensive" to compute than the PPID == 2 test, and therefore the least expensive test should be performed first so that the more

[sqlite] Query on TEMP view.

Hi All, I am facing a problem where in defined function registered to sqlite is called multiple time withput considering the filter. Ex: Table and entry: ID NAME PPID 1a.mp3 2 2b.mp3 3 Query: SELECT COUNT(TEMP.ID) FROM (SELECT ID,NAME,PPID FROM AUDIO WHERE PPID=2) AS TEMP

Re: [sqlite] RBU conflicts with SQLITE_UNTESTABLE

On 8/25/2018 4:53 PM, Richard Hipp wrote: There are lots of similar situations, where omitting features from SQLite will break extensions that depend on those features. For example SQLITE_OMIT_VIRTUALTABLE will break FTS3, FTS4, FTS5, and RTREE, all of which depend on virtual tables. Depend

Re: [sqlite] Unsigned

> On Aug 25, 2018, at 5:21 PM, D Burgess wrote: > > The data includes unsigned 32 bit integers which are stored as float > (don't ask me why, I guess the primary reason is the same reason that > 32bit Lua uses floats as integers). That seems like a mistake on their part, since unsigned 32-bit

Re: [sqlite] [EXTERNAL] Re: Unsigned

By definition, a pointer (the current virtual memory address of an object) only supports an equality test ("do these two pointers reference the same object"). There is no point in sorting pointers. But you can still do it by implementing a collating sequence which would internally do int pointe