]> git.ipfire.org Git - thirdparty/sqlite.git/commit
In an ORDER BY LIMIT, make sure the ORDER BY expression evaluator does not
authordrh <drh@noemail.net>
Sat, 5 May 2018 16:50:35 +0000 (16:50 +0000)
committerdrh <drh@noemail.net>
Sat, 5 May 2018 16:50:35 +0000 (16:50 +0000)
commitc6f36fa33ad4d2f8642331516ba1a7ed7af60b1b
tree1924709a852808fe764e8ebed21f4498cc2cd58d
parent6fcf83a50334a4bea413c8e078e28ba11e956cd8
In an ORDER BY LIMIT, make sure the ORDER BY expression evaluator does not
try to reuse values from the result set if the result set has not yet
be computed.  This fixes a bug in the recent deferred-row loading
optimization, check-in [c381f0ea57002a264fd958b28e].
OSSFuzz discovered the problem.

FossilOrigin-Name: 5d61e75f32de09c81dbe844443209f063cccb005d60b846900de5b023643fc3b
manifest
manifest.uuid
src/select.c
test/orderby1.test