aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authordan <dan@noemail.net>2018-03-31 16:31:51 +0000
committerdan <dan@noemail.net>2018-03-31 16:31:51 +0000
commit4f9a7e5cb74b07b33209cc39d7acdbc85fd0ea2a (patch)
tree5ce6577ea4d8a197f5b4edaa43751ecad9a42624 /src
parent58bd03320dce25523d8c7125b63dc16810a624cc (diff)
downloadsqlite-4f9a7e5cb74b07b33209cc39d7acdbc85fd0ea2a.tar.gz
sqlite-4f9a7e5cb74b07b33209cc39d7acdbc85fd0ea2a.zip
Fix an assertion failure triggered by a SELECT with a compound sub-query that
contains an incorrectly placed ORDER BY clause. This problem is just an assert() failure - non-DEBUG builds are not affected. Problem found by OSSFuzz. FossilOrigin-Name: 823779d31eb09cda5effe747d9adb35e600a52d4274226586437f674e7824d91
Diffstat (limited to 'src')
-rw-r--r--src/select.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/select.c b/src/select.c
index 4a8c3d22f..fa804f173 100644
--- a/src/select.c
+++ b/src/select.c
@@ -3773,7 +3773,6 @@ static int flattenSubquery(
pOrderBy->a[i].u.x.iOrderByCol = 0;
}
assert( pParent->pOrderBy==0 );
- assert( pSub->pPrior==0 );
pParent->pOrderBy = pOrderBy;
pSub->pOrderBy = 0;
}