History log of /sqlite-3.40.0/test/rowvalue3.test (Results 1 – 7 of 7)
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
# 48619160 01-Jun-2022 drh <>

New test cases for row values and RIGHT JOIN.

FossilOrigin-Name: 5f0582b90fab9111e4a645c692549c35480e62635c596f8c7fa3466bd22f7235


Revision tags: 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
# 54cda4ed 17-Nov-2016 drh <[email protected]>

Disable the query flattener optimization for SELECT statements that are on
the RHS of vector IN operators. This is a hack that fixes the bug
described in ticket [da7841375186386c]. A better solution

Disable the query flattener optimization for SELECT statements that are on
the RHS of vector IN operators. This is a hack that fixes the bug
described in ticket [da7841375186386c]. A better solution that does not
disable the query flattener is needed, but this will server for the time
being.

FossilOrigin-Name: 005d5b870625d175fdf3c0e87d974006c569d9e1

show more ...


Revision tags: version-3.15.1, version-3.15.0, version-3.14.2
# e835bc12 23-Aug-2016 drh <[email protected]>

Simplify the row value misuse error message.

FossilOrigin-Name: 838c50a5bf46fd0340839d577fa28ba02b4f2034


Revision tags: version-3.14.1, version-3.14.0
# d05a7144 02-Aug-2016 dan <[email protected]>

Fix a problem with vector range constraints and mixed ASC/DESC indexes.

FossilOrigin-Name: e2ad30c8b5366fd8e50f36c62345ed03ec613c47


# 145b4ea5 29-Jul-2016 dan <[email protected]>

Change the way "(a, b) = (SELECT *)" expressions are handled in where.c if there is an index on one of the columns only.

FossilOrigin-Name: 4dfebff2924f46284d5b9cda69175f79b29d6028


# 8da209b1 26-Jul-2016 dan <[email protected]>

Fix where.c handling of "IN (SELECT ...)" expressions when the SELECT returns more than one result column. Also error handling for other row value constructor cases.

FossilOrigin-Name: 061b8006034f0

Fix where.c handling of "IN (SELECT ...)" expressions when the SELECT returns more than one result column. Also error handling for other row value constructor cases.

FossilOrigin-Name: 061b8006034f06a0311b4304c8b14d2c8b0153df

show more ...


# ba00e30a 23-Jul-2016 dan <[email protected]>

Allow vector IN(SELECT ...) expressions to use an index if either all the indexed columns are declared NOT NULL or if there is no difference between the expression evaluating to 0 and NULL (as in a W

Allow vector IN(SELECT ...) expressions to use an index if either all the indexed columns are declared NOT NULL or if there is no difference between the expression evaluating to 0 and NULL (as in a WHERE clause).

FossilOrigin-Name: e2fd6f49b1b145bec09c581cc982b89429643ae9

show more ...