blob: dd9284acf6d917e3f08a43630ce5456babda2de5 [file] [log] [blame]
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
From: Darwin Huang <huangdarwin@chromium.org>
Date: Wed, 1 May 2019 14:44:32 -0700
Subject: [PATCH 1/8] Don't generate VDBE code for VACUUM after a syntax error
This backports https://www.sqlite.org/src/info/930842470da27d72
Bug: https://crbug.com/954777
---
third_party/sqlite/patched/src/vacuum.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/third_party/sqlite/patched/src/vacuum.c b/third_party/sqlite/patched/src/vacuum.c
index 4cf91f8d0ada..3ec765df8a49 100644
--- a/third_party/sqlite/patched/src/vacuum.c
+++ b/third_party/sqlite/patched/src/vacuum.c
@@ -106,6 +106,7 @@ void sqlite3Vacuum(Parse *pParse, Token *pNm, Expr *pInto){
Vdbe *v = sqlite3GetVdbe(pParse);
int iDb = 0;
if( v==0 ) goto build_vacuum_end;
+ if( pParse->nErr ) goto build_vacuum_end;
if( pNm ){
#ifndef SQLITE_BUG_COMPATIBLE_20160819
/* Default behavior: Report an error if the argument to VACUUM is
--
2.21.0