Hi Bill
Yes - we should certainly stick to standards wherever possible, and your
suggestion sounds like a good approach. I can't promise when I'll get around
to doing this though. Of course, if you've got the spare time, it's in
CVS... :-)
Pete
-----Original Message-----
From: Bill Karwin <bill.karwin@lutris.com>
To: instantDB@enhydra.org <instantDB@enhydra.org>
Date: 14 August 2000 21:54
Subject: Re: InstantDB: Re: IND bug report
>Regarding SET LITERALS STRICT_ON making all quoted strings be string
>literals.
>
>Quoted identifers are important to allow object names to contain SQL
>reserved words, whitespace, lower case, or non-ASCII character sets.
>
>The SQL standard specifies that double-quoted strings are delimited
>identifiers of objects, and single-quoted strings are string literals.
>
>This avoids the ambiguity mentioned in the URL you give below, in a
>different way than the SET LITERALS property.
>
>What's the possibility for InstantDB to implement this? I'd suggest a
>new argument for SET LITERALS, perhaps SET LITERALS STANDARD, that makes
>the SQL parser adhere to the SQL standard for quoted identifiers vs.
>string literals.
>
>Regards,
>Bill Karwin
>
>Peter Hearty wrote:
>>
>> Have a look at:
>>
>>
http://instantdb.enhydra.org/software/documentation/types.html#StringLiteral
s
>---------------------------------------------------------------------------
--
>To unsubscribe from this mailing list, send email to majordomo@enhydra.org
>with the text "unsubscribe instantdb" in the body of the email.
>If you have other questions regarding this mailing list, send email to
>the list admin at owner-instantdb@enhydra.org.
>
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|