History log of /sqlite-3.40.0/test/where4.test (Results 1 – 11 of 11)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: release, version-3.50.2, version-3.50.1, major-release, version-3.50.0, version-3.49.2, patch-release, version-3.44.4, version-3.49.1, version-3.49.0, major-relase, relase, version-3.48.0, version-3.47.2, version-3.47.1, version-3.47.0, version-3.46.1, version-3.46.0, version-3.45.3, version-3.44.3, version-3.45.2, version-3.45.1, vesion-3.45.1, version-3.45.0, version-3.44.2, version-3.44.1, version-3.44.0, version-3.43.2, version-3.43.1, version-3.43.0, version-3.42.0, version-3.41.2, version-3.41.1, version-3.41.0, version-3.40.1, version-3.40.0, version-3.39.4, version-3.39.3, version-3.39.2, version-3.39.1, version-3.39.0, version-3.38.5, version-3.38.4, relese, version-3.38.3, version-3.38.2, version-3.38.1, version-3.38.0, version-3.37.2, version-3.37.1, version-3.37.0, version-3.36.0, version-3.35.5, version-3.35.4, version-3.35.3, same-as-3.35.3, version-3.35.2, version-3.35.1, version-3.35.0, patch, version-3.34.1, version-3.34.0, version-3.33.0, version-3.32.3, version-3.32.2, version-3.32.1, version-3.32.0, version-3.31.1, version-3.31.0, version-3.30.1, version-3.30.0, version-3.29.0, version-3.28.0, version-3.27.2, version-3.27.1, version-3.27.0, version-3.26.0, version-3.25.3, version-3.25.2, version-3.25.1, version-3.25.0, version-3.24.0, version-3.23.2, version-3.23.1, version-3.23.0, version-3.22.0, version-3.21.0, version-3.20.1, version-3.19.4, version-3.20.0, version-3.18.2, version-3.18.1, version-3.19.3, version-3.19.2, version-3.19.1, version-3.19.0, version-3.18.0, version-3.17.0, version-3.16.2, version-3.16.1, version-3.16.0, version-3.15.2, version-3.15.1, version-3.15.0, version-3.14.2, version-3.14.1, version-3.14.0, version-3.13.0, version-3.12.2, version-3.12.1, version-3.9.3, version-3.12.0, version-3.11.1, version-3.11.0, version-3.10.2, version-3.10.1, version-3.10.0
# b1d607de 05-Nov-2015 drh <[email protected]>

Improvements and simplifications to the equality seek logic. Tests are
adjusted so that they all pass now.

FossilOrigin-Name: 997ce6c90b454c03cc2ef6934752ee8dd2e520e3


Revision tags: version-3.9.2, version-3.9.1, version-3.9.0
# edb04ed9 04-Sep-2015 drh <[email protected]>

Continue to support the (broken) legacy syntax of allowing strings for
column names in CREATE INDEX statements and in UNIQUE and PRIMARY KEY
constraints.

FossilOrigin-Name: 3d3df79bfaf9dbc7aa711c08a

Continue to support the (broken) legacy syntax of allowing strings for
column names in CREATE INDEX statements and in UNIQUE and PRIMARY KEY
constraints.

FossilOrigin-Name: 3d3df79bfaf9dbc7aa711c08a19d2f6dbe744b32

show more ...


Revision tags: version-3.8.11.1, version-3.8.11, version-3.8.10.2
# 3072b537 15-May-2015 dan <[email protected]>

Do not assume that "col IS ?" matches at most a single row of a UNIQUE column unless the column is also NOT NULL.

FossilOrigin-Name: e038ce8955e785afcc07bb22499955bbd22a7af4


# e8d0c61f 14-May-2015 drh <[email protected]>

A new implementation of indexing with the IS operator that works correctly
when the IS operator is in the WHERE clause and the operands are from
opposite sides of a LEFT JOIN.

FossilOrigin-Name: 45

A new implementation of indexing with the IS operator that works correctly
when the IS operator is in the WHERE clause and the operands are from
opposite sides of a LEFT JOIN.

FossilOrigin-Name: 4541688b3f56f5cd3d5b299594b58c577ad633bb

show more ...


Revision tags: version-3.8.10.1, version-3.8.10, version-3.8.9, version-3.8.8.3, version-3.8.8.2, version-3.8.8.1, version-3.8.8, version-3.8.7.4, version-3.8.7.3, version-3.8.7.2, version-3.8.7.1, version-3.8.6.1, version-3.8.7, version-3.8.6, version-3.8.5, version-3.8.4.3, version-3.8.4.2, version-3.8.4.1, version-3.8.4
# cfc6ca41 14-Feb-2014 drh <[email protected]>

Seek past NULLs in a top-constrained search. Avoid checking for NULLs in
the body of the search.

FossilOrigin-Name: e07a32f30862acf3b322d4d8deb015846d6f8f5f


Revision tags: version-3.8.3.1, version-3.8.3, version-3.8.2, version-3.8.1, version-3.8.0.2, version-3.8.0.1, version-3.8.0, version-3.7.17, version-3.7.16.2, version-3.7.16.1, version-3.7.16, version-3.7.15.2, version-3.7.15.1, version-3.7.15, version-3.7.14.1, version-3.7.14, version-3.7.13, version-3.7.12.1, version-3.7.12, mountain-lion, version-3.7.11, version-3.7.10, version-3.7.9, version-3.7.8, version-3.7.7.1, version-3.7.7, version-3.7.6.3, version-3.7.6.2, version-3.7.6.1, version-3.7.6, version-3.7.5, version-3.7.4, experimental, version-3.7.2, fts3-refactor, cvs-to-fossil-cutover, version-3.6.15, version-3.6.10
# 284f4aca 10-Dec-2007 danielk1977 <[email protected]>

Fix compilation/testing with OMIT_SUBQUERY defined. Ticket #2828. (CVS 4603)

FossilOrigin-Name: 0b34a18651764e650faba983be8593992ab2f4a9


# 4152e677 12-Sep-2007 danielk1977 <[email protected]>

Fixes for compilation/testing when the various OMIT macros are defined. (CVS 4423)

FossilOrigin-Name: c8405b15c074c94dab5e33272cf1471f458d11df


# 39984cdc 02-Jun-2007 danielk1977 <[email protected]>

Fix a vdbe stack leak that could occur where one side of a WHERE clause inequality evaluated to SQL null. (CVS 4045)

FossilOrigin-Name: 17152bf1a268e130f0c43046bb438b617a747ff5


# 72e8fa42 28-Mar-2007 drh <[email protected]>

Correctly handle NULLs in IN operators. Ticket #2273.
The changes in where.c and in the WhereLevel.aInLoop structure are
not strictly necessary to fix this problem - they just make the code
easier t

Correctly handle NULLs in IN operators. Ticket #2273.
The changes in where.c and in the WhereLevel.aInLoop structure are
not strictly necessary to fix this problem - they just make the code
easier to read. Only the change in OP_Next/OP_Prev operator of vdbe.c
is required. (CVS 3735)

FossilOrigin-Name: 26348556d824c032851e409ac510cddb55c200bf

show more ...


# f2d315d0 25-Jan-2007 drh <[email protected]>

Fix an additional problem with the IS NULL optimization on LEFT JOINs.
Ticket #2189. See also ticket #2177. (CVS 3602)

FossilOrigin-Name: 358dd82d3a921228155e2cf9e22aedd2b651ca9c


# c49de5d9 19-Jan-2007 drh <[email protected]>

Make sure the IS NULL optimization introduced by check-in (3494) correctly
handles a LEFT JOIN where the a term from the right table of the join uses
an IS NULL constraint. Ticket #2177. This check

Make sure the IS NULL optimization introduced by check-in (3494) correctly
handles a LEFT JOIN where the a term from the right table of the join uses
an IS NULL constraint. Ticket #2177. This check-in also adds the new test
cases that were suppose to have been added with (3494) but which were
mistakenly omitted. (CVS 3595)

FossilOrigin-Name: 335863e4d16113fb9ecebce35d2db043771d98b1

show more ...