Re: [sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

Thanks a ton for the replies. This pretty much confirms what I've been suspecting. On 3 February 2017 at 11:24, Clemens Ladisch wrote: > The FTS and R-tree virtual tables do not contain NULL values, so > I guess it was never seen as necessary. Does this make it an accidental

Re: [sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

The supported constraints are: #define SQLITE_INDEX_CONSTRAINT_EQ 2 #define SQLITE_INDEX_CONSTRAINT_GT 4 #define SQLITE_INDEX_CONSTRAINT_LE 8 #define SQLITE_INDEX_CONSTRAINT_LT 16 #define SQLITE_INDEX_CONSTRAINT_GE 32 #define SQLITE_INDEX_CONSTRAINT_MATCH 64 #define

Re: [sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

Daniel Kamil Kozar wrote: > I'd like to ask why using a IS NULL or IS NOT NULL constraint in a > query made to a virtual table does not result in these constraints > being present in the sqlite3_index_info structure passed to the > virtual table's xBestIndex. Because there is no

[sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

Hi. I'd like to ask why using a IS NULL or IS NOT NULL constraint in a query made to a virtual table does not result in these constraints being present in the sqlite3_index_info structure passed to the virtual table's xBestIndex. Currently, using one of these constraints results in no constraints