|
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 |
|
| #
40386968 |
| 22-Oct-2020 |
drh <[email protected]> |
Sometimes it makes sense to do a full table scan rather than try to use
an index when most of the rows will be selected. This branch is trying to
tune the query planner to make that happen more ofte
Sometimes it makes sense to do a full table scan rather than try to use
an index when most of the rows will be selected. This branch is trying to
tune the query planner to make that happen more often.
FossilOrigin-Name: 0f42099ad65855c94af8472f3a6fddac7fc2a82e8fdfcc06a298eb6683a28688
show more ...
|
|
Revision tags: 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 |
|
| #
66c48907 |
| 29-Oct-2019 |
drh <[email protected]> |
Remove the legacy_file_format PRAGMA. In its place, provide the
SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config().
Fix for ticket [6484e6ce678fffab]
FossilOrigin-Name: 4d424f3047b48f
Remove the legacy_file_format PRAGMA. In its place, provide the
SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config().
Fix for ticket [6484e6ce678fffab]
FossilOrigin-Name: 4d424f3047b48fc441475137f30a719d2f079390c86fe2617710ddfb05c5e240
show more ...
|
|
Revision tags: version-3.30.1, version-3.30.0 |
|
| #
f7c92e82 |
| 21-Aug-2019 |
dan <[email protected]> |
Avoid assuming that "column IS ?", where column is declared UNIQUE, matches only a single row (as "?" might be NULL). Fix for [b8689402].
FossilOrigin-Name: d02490a2f0cae047087130b4ad8f55f265845c2ff
Avoid assuming that "column IS ?", where column is declared UNIQUE, matches only a single row (as "?" might be NULL). Fix for [b8689402].
FossilOrigin-Name: d02490a2f0cae047087130b4ad8f55f265845c2ffb3bde3b7d507edb54acea6d
show more ...
|
| #
a79a0e73 |
| 29-Jul-2019 |
dan <[email protected]> |
When using an index for both DISTINCT and ORDER BY, do not confuse the number of columns required for distinctness with the number required to get the correct sort order. Fix for [6749cb3c].
FossilO
When using an index for both DISTINCT and ORDER BY, do not confuse the number of columns required for distinctness with the number required to get the correct sort order. Fix for [6749cb3c].
FossilOrigin-Name: b47169319ad88e8ffdbe8fbb91f4cced81ebd5c0ee1b018be2d0256c9a1c5159
show more ...
|
|
Revision tags: 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 |
|
| #
fa337cc1 |
| 23-Nov-2017 |
drh <[email protected]> |
Completely disable the skip-ahead-distinct optimization for all but the
inner-most loop of a DISTINCT join. Fix for ticket [ef9318757b152e3a26e9592]
FossilOrigin-Name: b7595cf2cadcba486e60b3c230ccc
Completely disable the skip-ahead-distinct optimization for all but the
inner-most loop of a DISTINCT join. Fix for ticket [ef9318757b152e3a26e9592]
FossilOrigin-Name: b7595cf2cadcba486e60b3c230ccc412a7cf449c1d56cbe65869e6d5d9f1374d
show more ...
|
| #
065b34f6 |
| 21-Nov-2017 |
drh <[email protected]> |
Fix the skip-ahead-distinct optimization on joins for cases there the table
in the inner loop of the join does not contribute any columns to the
result set. Proposed fix for ticket [ef9318757b152e3a
Fix the skip-ahead-distinct optimization on joins for cases there the table
in the inner loop of the join does not contribute any columns to the
result set. Proposed fix for ticket [ef9318757b152e3a2]
FossilOrigin-Name: 2dcef5a9ae7f347da65207bf6bf612fb12e18e1a6704799322f0cf2a86154cfd
show more ...
|
|
Revision tags: 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 |
|
| #
172806e4 |
| 13-Apr-2017 |
drh <[email protected]> |
Fix the skip-ahead-distinct optimization so that it works with indexes that
have repeated columns with different collating sequences.
FossilOrigin-Name: ce1e2b88777e00a82c04abe5ba35eec81b5f324e462f0
Fix the skip-ahead-distinct optimization so that it works with indexes that
have repeated columns with different collating sequences.
FossilOrigin-Name: ce1e2b88777e00a82c04abe5ba35eec81b5f324e462f099cd00b21054f369688
show more ...
|
| #
a74f5c29 |
| 13-Apr-2017 |
dan <[email protected]> |
New test cases and minor fixes for the optimization on this branch.
FossilOrigin-Name: 70ac9ea1a6cb2f4906f00f1a04f668e5ba5eeed8d4d0fa4be57a9c9eb0683697
|
| #
8489bf5a |
| 13-Apr-2017 |
drh <[email protected]> |
Forward port the skip-ahead-distinct branch which was abandoned for some reason
that I do not recall. This port should have been achived by a merge of trunk
into the previous head of skip-ahead-dist
Forward port the skip-ahead-distinct branch which was abandoned for some reason
that I do not recall. This port should have been achived by a merge of trunk
into the previous head of skip-ahead-distinct, but that did not work. So I had
to manually "rebase" the changes.
FossilOrigin-Name: 132339a1fb0b9664df4d3eefbed6e77ef100ba95a91dcc622da7bd3fcdfcd6af
show more ...
|