drh
|
6ee5a7b481
|
Fix multiple issues with the ORDER BY LIMIT optimization. This is the
proposed resolution to ticket [9936b2fa443fec03ff25].
FossilOrigin-Name: 206720129ed2fa8875a286266d05b99fb2caf8671e4b74b26a6286a2073fcd8b
|
2018-09-08 20:09:46 +00:00 |
|
drh
|
472e41ea16
|
Correctly invalidate a column cache line when it is overwritten with NULL.
Fix for ticket [123c9ba32130a6c9d432].
FossilOrigin-Name: 65754dc3b830ef9482655d2e93c2cd4acaa7a8715a58d8309955d04378541f89
|
2017-12-13 18:01:52 +00:00 |
|
dan
|
83465a662f
|
Fix a problem affecting queries that match the pattern (... WHERE ipk IN (....) ORDER BY ? LIMIT ?). Fix for [96c1454c].
FossilOrigin-Name: 8e2b25f9b8a7ed087d3cece74239814bee19429e
|
2016-10-12 14:48:00 +00:00 |
|
drh
|
8dd099bbaa
|
New test case for the ORDER BY LIMIT optimization.
FossilOrigin-Name: 9a5a489d0d344274d0fc9fb9303503a454f42844
|
2016-09-23 18:13:01 +00:00 |
|
drh
|
57a8c61501
|
The ORDER BY LIMIT optimization is not valid unless the inner-most IN operator
loop is actually used by the query plan.
Fix for ticket [0c4df46116e90f92].
FossilOrigin-Name: 820644b886f81e991fceb5f1c3290b8959b34528
|
2016-09-07 01:51:46 +00:00 |
|
drh
|
dd545d3bf2
|
Make sure the ORDER BY LIMIT optimization is not applied if the inner-most
loop can only have a single iteration and is hence not really a loop.
FossilOrigin-Name: 13e3bd3de6b434b6182ef36be108d7ee0be8ca53
|
2016-08-04 09:09:44 +00:00 |
|
drh
|
73fa4737ce
|
A few simple test cases for the ORDER BY LIMIT optimization.
FossilOrigin-Name: 08849eab0f6ef29eaf6d2ce9c692de9b953dbd27
|
2016-05-20 00:21:42 +00:00 |