Double Quoted Literals now treated as identifiers in current trunk, causing errors.

(1) By Kevin Youren (KevinYouren) on 2023-04-16 04:03:52 [link] [source]

Please note I have a few errors, such as:

Parse error near line 81: no such column: SELECT '
  SELECT "SELECT '" || name || " ',COUNT(*) FROM main."|| name || "; " FROM sqli
         ^--- error here

Parse error near line 1: no such column: 2E7411597411255D
  UPDATE directories SET dir_uuid_short = "2E7411597411255D" WHERE dir_name LIKE
                            error here ---^

Please let me know if this is a permanent change, as a bit of re-programming will be required.

(2) By Larry Brasfield (larrybr) on 2023-04-16 04:08:56 in reply to 1 [link] [source]

Read item #8 in quirks. It explains the cause of your issue in some detail and provides a work-around.

The change is permanent. Accepting double-quoted string literals is regarded as a misfeature due to experience with problems it causes. The misfeature is not coming back as a default, but it can be summoned by those who strangely like it.

(3) By Kevin Youren (KevinYouren) on 2023-04-16 04:33:47 in reply to 2 [link] [source]

Thanks, Larry.

I will treat it as permanent.

(4) By anonymous on 2023-04-16 10:04:40 in reply to 2 [source]

Small typo: this item refers to "SQLITE_DBCONFIG_DQS_DLL" instead of "SQLITE_DBCONFIG_DQS_DDL".