diff options
| author | drh <> | 2024-02-11 20:53:14 +0000 |
|---|---|---|
| committer | drh <> | 2024-02-11 20:53:14 +0000 |
| commit | 3c5a810646a060aeb3019942bf66278168df8f3b (patch) | |
| tree | 2306069c2c6abf234929b2ae66d2b8b0dfe73ac4 /src/resolve.c | |
| parent | ece3567aec217b9e302e56295968966d8d7a3782 (diff) | |
| download | sqlite-3c5a810646a060aeb3019942bf66278168df8f3b.tar.gz sqlite-3c5a810646a060aeb3019942bf66278168df8f3b.zip | |
If a term of an ORDER BY or GROUP BY contains an aggregate function or column,
then it is not an alias that needs to be resolved, so don't try to. This fixes
a harmless assertion found by dbsqlfuzz. This yet another problem that
orginated at check-in [6e6b3729e0549de0].
FossilOrigin-Name: d4ec2a5d2297cd9ead0a8768dcf003ea76c74d8d68d88c40f62363f484a4a4d3
Diffstat (limited to 'src/resolve.c')
| -rw-r--r-- | src/resolve.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/resolve.c b/src/resolve.c index 29975f385..5d0801e82 100644 --- a/src/resolve.c +++ b/src/resolve.c @@ -79,6 +79,8 @@ static void resolveAlias( assert( iCol>=0 && iCol<pEList->nExpr ); pOrig = pEList->a[iCol].pExpr; assert( pOrig!=0 ); + assert( !ExprHasProperty(pExpr, EP_Reduced|EP_TokenOnly) ); + if( pExpr->pAggInfo ) return; db = pParse->db; pDup = sqlite3ExprDup(db, pOrig, 0); if( db->mallocFailed ){ |