-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/13 14:27, Simon Slavin wrote:
> Any chance of killing it in SQLite 4 ?
Continuing to beat a truly dead horse, it would be nice to help developers
fix their existing codebase via something like an additional "lint mode".
On Sun, Feb 10, 2013 at 5:27 PM, Simon Slavin wrote:
>
> On 10 Feb 2013, at 8:39pm, Richard Hipp wrote:
>
> > The fact that SQLite will treat a double-quoted string as a string
> literal
> > rather than as a quoted identifier is a horrible mis-feature. It
On 10 Feb 2013, at 8:39pm, Richard Hipp wrote:
> The fact that SQLite will treat a double-quoted string as a string literal
> rather than as a quoted identifier is a horrible mis-feature. It was added
> 10 years or so ago in an attempt to be more MySQL-compatible. I have come
Hi Richard,
Thank you for taking the time to reply. Personally I never use
double-quoted strings as string literals, but this issue was reported by
users of a tool that generates table creation SQL based on user input, and
that encloses in parenthesis any default values entered by the user to
The fact that SQLite will treat a double-quoted string as a string literal
rather than as a quoted identifier is a horrible mis-feature. It was added
10 years or so ago in an attempt to be more MySQL-compatible. I have come
to sorely regret that change. I'd love to get rid of this mis-feature,
5 matches
Mail list logo