MXS-3408 Fix leak in qc_sqlite
Without this fix, there will be a leak every time a SELECT statement uses ... PRECEDING or ... FOLLOWING (except for the case when ... is UNBOUNDED).
This commit is contained in:
@ -2060,11 +2060,15 @@ wf_frame_units ::= ROWS.
|
||||
|
||||
wf_frame_start ::= UNBOUNDED PRECEDING.
|
||||
wf_frame_start ::= CURRENT ROW.
|
||||
wf_frame_start ::= term PRECEDING.
|
||||
wf_frame_start ::= term(X) PRECEDING. {
|
||||
sqlite3ExprDelete(pParse->db, X.pExpr);
|
||||
}
|
||||
|
||||
wf_frame_bound ::= wf_frame_start.
|
||||
wf_frame_bound ::= UNBOUNDED FOLLOWING.
|
||||
wf_frame_bound ::= term FOLLOWING.
|
||||
wf_frame_bound ::= term(X) FOLLOWING. {
|
||||
sqlite3ExprDelete(pParse->db, X.pExpr);
|
||||
}
|
||||
|
||||
wf_frame_extent ::= wf_frame_start.
|
||||
wf_frame_extent ::= BETWEEN wf_frame_bound AND wf_frame_bound.
|
||||
|
Reference in New Issue
Block a user