If it was called "PRAGMA strict_mode" or even "PRAGMA disable_dbl_quot_lit" you
could reverse the check and then the default behavior would remain the same.
--- On Fri, 11/16/12, NSRT Mail account. wrote:
From: NSRT Mail account.
Subject: Re: [sqlite] Stricter parsin
r patch of course
would keep the default behavior. Although I couldn't figure out the pragma
system enough to see how to specify what default pragma settings are.
From: Dan Freundel
To: General Discussion of SQLite Database
Sent: Thursday, November
Hello Everyone,
I'm glad to see I'm not the only one who wants this.
I'm thinking perhaps I wasn't clear enough in my first e-mail that I created a
patch for the time being.
You can download the patch, along with already modified source, static
libraries and binaries for Linux i386, Linux AMD64
3763/is-there-a-way-disable-lax-quoting-rules-in-sqlite/
--- On Thu, 11/15/12, John Gabriele wrote:
From: John Gabriele
Subject: Re: [sqlite] Stricter parsing rules
To: "General Discussion of SQLite Database"
Date: Thursday, November 15, 2012, 1:56 PM
On Wed, Nov 14, 2012 at 5:2
On Wed, Nov 14, 2012 at 5:22 PM, Simon Slavin wrote:
>
> On 14 Nov 2012, at 9:46pm, BareFeetWare wrote:
>
>> I agree. this tolerance by SQLite for misquoted identifiers allows a lot of
>> errors. I'd really like to see the rules tightened to remove ambiguous input.
>
> Me three. Perhaps this an
The behaviour of quoting with [identifier] or `identifier` seems to do what
you want, but, as the docs say, these are not standard SQL.
http://www.sqlite.org/lang_keywords.html
It's not a great option, since it forces you to have nonstandard SQL, but
it's a potentially useful one to have on the t
On 14 Nov 2012, at 9:46pm, BareFeetWare wrote:
> I agree. this tolerance by SQLite for misquoted identifiers allows a lot of
> errors. I'd really like to see the rules tightened to remove ambiguous input.
Me three. Perhaps this and a couple of similar things will be fixed in SQLite4.
Simon.
I agree. this tolerance by SQLite for misquoted identifiers allows a lot of
errors. I'd really like to see the rules tightened to remove ambiguous input.
Thanks,
Tom
Tom Brodhurst-Hill
BareFeetWare
--
iPhone/iPad/iPod and Mac software development, specialising in databases
develo...@barefeetwar
In accordance with SQL standards and SQLite developing guidelines, my entire
team always uses double quotes around identifiers, and single quotes around
string literals.
Some relevant documentation is here: http://www.sqlite.org/lang_keywords.html
"SQLite adds new keywords from time to time when
9 matches
Mail list logo
