aboutsummaryrefslogtreecommitdiff
path: root/src/sqliteInt.h
diff options
context:
space:
mode:
authordan <dan@noemail.net>2019-05-20 17:14:25 +0000
committerdan <dan@noemail.net>2019-05-20 17:14:25 +0000
commit0d92571d65393ae87f01f533eee2a6075b122efc (patch)
tree88ae798a8847dbf46b4d58d341de8c6e329c96e3 /src/sqliteInt.h
parent8ac02a94ab5ee7496c053c417a77bc620bb548fb (diff)
downloadsqlite-0d92571d65393ae87f01f533eee2a6075b122efc.tar.gz
sqlite-0d92571d65393ae87f01f533eee2a6075b122efc.zip
Disallow string constants enclosed in double-quotes within new CREATE TABLE and CREATE INDEX statements. It is still possible to enclose column names in double-quotes, and existing database schemas that use double-quotes for strings can still be loaded. This addresses ticket [9b78184b].
FossilOrigin-Name: 1685610ef8e0dc9218b02461ceab14dc6114f4f5ef7fcda0da395094aff443e1
Diffstat (limited to 'src/sqliteInt.h')
-rw-r--r--src/sqliteInt.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/sqliteInt.h b/src/sqliteInt.h
index 6f7b18109..fc4b46002 100644
--- a/src/sqliteInt.h
+++ b/src/sqliteInt.h
@@ -2766,7 +2766,7 @@ struct NameContext {
NameContext *pNext; /* Next outer name context. NULL for outermost */
int nRef; /* Number of names resolved by this context */
int nErr; /* Number of errors encountered while resolving names */
- u16 ncFlags; /* Zero or more NC_* flags defined below */
+ int ncFlags; /* Zero or more NC_* flags defined below */
Select *pWinSelect; /* SELECT statement for any window functions */
};
@@ -2793,6 +2793,7 @@ struct NameContext {
#define NC_Complex 0x2000 /* True if a function or subquery seen */
#define NC_AllowWin 0x4000 /* Window functions are allowed here */
#define NC_HasWin 0x8000 /* One or more window functions seen */
+#define NC_NewSchema 0x10000 /* Currently resolving self-refs for new object */
/*
** An instance of the following object describes a single ON CONFLICT