Eugene Wee wrote:
>>
>> If it does not have any compatibility with any other database,
>> ONLY then I say that one should drop #3 quoting convention.
>>
> I believe that MySQL allows double quotes to be used as string
> delimiters by default, but then this would not be a compatibility break
>
> 3. Double-quoted names fall back to being string literals if
> there is no matching table or column name.
>
> In retrospect, (3) seems to be a bad idea. It is accident-prone and
> leads to all kinds of confusion. For example, if double-quotes are
> being used correctly (which is to say to quot
Hi,
palmer ristevski wrote:
> He is my vote.
> I like the fact that conventions #1 and #2 make things compatible with other
> databases.
> Does #3, by chance, do the same with another database not mentioned
> (eg. Oracle).
>
> If it does not have any compatibility with any other database,
> ONLY
Yes, please remove #3. Now is a particularly good time for it seeing as
the 3.6 line is quite new.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
D. Richard Hipp wrote:
> 3. Double-quoted names fall back to being string literals if
> there is no matching table or column name.
>
> So I'm giving some thought to removing feature (3) above and
> disallowing double-quoted string literals. My concern is, though,
> that this might brea
He is my vote.
I like the fact that conventions #1 and #2 make things compatible with other
databases.
Does #3, by chance, do the same with another database not mentioned
(eg. Oracle).
If it does not have any compatibility with any other database,
ONLY then I say that one should drop #3 quoting
+1 for removal of quote munging.
RW
Ron Wilson, S/W Systems Engineer III, Tyco Electronics, 434.455.6453
sqlite>select level from sqlGuruOMeter where name="Ron Wilson";
2
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of D. Richard Hipp
Sent: Thursday, Au
+1 in favor of removing non-standard quoting mechanism #3.
- Original Message
From: D. Richard Hipp <[EMAIL PROTECTED]>
To: General Discussion of SQLite Database
Sent: Thursday, August 7, 2008 10:26:07 AM
Subject: [sqlite] Proposed removal of (mis-)feature
String literals in SQL are s
Henceforth and forward: Let the standards violator suffer his just
rewards!" :-)
Dr., your just trying to supply the worlds greatest database, not take a
bunch of slovenly coders to raise...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of D. Richard Hipp
S
On Thu, Aug 7, 2008 at 2:13 PM, Kees Nuyt <[EMAIL PROTECTED]> wrote:
>
> On Thu, 7 Aug 2008 13:26:07 -0400, drh wrote:
>
> [snip]
>
>>So I'm giving some thought to removing feature (3) above and
>>disallowing double-quoted string literals. My concern is, though,
>>that this might break many existi
+3 on removal of #3
Noah
--- On Thu, 8/7/08, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
From: D. Richard Hipp <[EMAIL PROTECTED]>
Subject: [sqlite] Proposed removal of (mis-)feature
To: "General Discussion of SQLite Database"
Date: Thursday, August 7, 2008, 12:26 PM
String literals in SQL are
On Thu, 7 Aug 2008 13:26:07 -0400, drh wrote:
[snip]
>So I'm giving some thought to removing feature (3) above and
>disallowing double-quoted string literals. My concern is, though,
>that this might break many existing applications.
>
>What opinion do you, gentle users, have of this matter?
Remove it. Better now than never.
Mike
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von D.
> Richard Hipp
> Gesendet: Donnerstag, 7. August 2008 19:26
> An: General Discussion of SQLite Database
> Betreff: [sqlite] Proposed removal of (mis
On Thu, Aug 07, 2008 at 01:26:07PM -0400, D. Richard Hipp wrote:
> 3. Double-quoted names fall back to being string literals if
> there is no matching table or column name.
>
[..]
> So I'm giving some thought to removing feature (3) above and
> disallowing double-quoted string literals.
I am quite mixed, because I've had people who are working on
substantial apps have things happen which came down to this problem.
So, on the one hand, I wish it had never been this way, but, on the
other hand, if it changes I'm going to hear about it.
My best hope would be a PRAGMA or some other s
On Thu, Aug 7, 2008 at 1:26 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> String literals in SQL are suppose to be enclosed in single-quotes -
> Pascal-style. Double-quotes are used around table and/or column names
> in cases where the name would otherwise be a keyword or when the name
> conta
+2 on removal of #3.
--- On Thu, 8/7/08, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
From: D. Richard Hipp <[EMAIL PROTECTED]>
Subject: [sqlite] Proposed removal of (mis-)feature
To: "General Discussion of SQLite Database"
Date: Thursday, August 7, 2008, 12:26 PM
String literals in SQL are suppo
I'm +1 on this change.
While I have not run into it as a feature or mis-feature, I would concur
that it is ambiguous and problematic. A simple clear syntax benefits
everyone.
BTW, Thanks for all you effort to produce this wonder software.
Best regards,
-Steve W
D. Richard Hipp wrote:
> Str
18 matches
Mail list logo
