| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Reshat Sabiq" <sabiq(at)purdue(dot)edu> |
| Cc: | paul(at)entropia(dot)co(dot)uk, "'Chris Boget'" <chris(at)wild(dot)net>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Simple query question |
| Date: | 2002-12-23 18:01:58 |
| Message-ID: | 6631.1040666518@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Reshat Sabiq" <sabiq(at)purdue(dot)edu> writes:
> I believe Oracle requires singles for values too. That must be a
> standard.
It is. SQL92 contains
<double quote> ::= "
<quote> ::= '
<delimited identifier> ::=
<double quote> <delimited identifier body> <double quote>
<character string literal> ::=
[ <introducer><character set specification> ]
<quote> [ <character representation>... ] <quote>
[ { <separator>... <quote> [ <character representation>... ] <quote> }... ]
I can't believe that MySQL gets such a basic element of SQL syntax wrong
--- perhaps the OP is mistaken? If MySQL really does treat doublequote
as introducing a literal, how do they handle weird identifiers, like
names with embedded spaces?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paesold | 2002-12-23 18:20:01 | Re: Simple query question |
| Previous Message | Devinder K Rajput | 2002-12-23 17:33:45 | performance question |