Monty Taylor wrote:
Roland Bouman wrote:
Hi!
Bill Culp wrote:
Is Drizzle going to support that awful back tick quote `for non standard
object names like this`?
Not sure. Opinions anyone? Certainly whoever tackles the blueprint
below could look at this behaviour...
Personally I would like to see the backtick banned, and (in accordance
with the standard) the single quote for string delimiters and the
double quote for identifiers.
That said, I know quite a few people feel that they should be able to
use both the double quote and single quote as string delimiters.
(At least, I raised the issue once on IRC and that seemed to be the
general opinion at the time.)
Yup. I'm one of those people. :)
So if the backtick is to be removed, and people still want to use both
double quotes and single quotes for string delimiters, then that means
you either drop support for quoted identifiers, or introduce a new
(non-standard) delimiter for identifiers. (Neither of which seems
desirable to me)
I would be most in favor of just getting rid of the facility of having
quoted identifiers. It seems to me that it mostly just causes pain and
suffering.
Quoted identifiers are part of the SQL language and are very commonly
used. Other database systems support them. MySQL has supported them.
If you don't like them, don't use them. Plenty of other people like them.
But if you're going to have them, they should follow standard
semantics. On the other hand, if you want to start over from scratch,
I've got all sorts of good ideas...
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
