Why are unquoted identifiers upper-cased per SQL-92?
6
votes
3
answers
1049
views
Section 5.6 of the SQL-92 standard contains rules 10...13 per which unquoted identifiers should be upper-cased, so
foo
becomes FOO
but "foo"
remains foo
.
These rules are respected by Oracle , IBM DB2, Snowflake , and ksqlDB but not by Postgres , MySQL or SQLite, for example.
The question is, why? In my understanding, the optional quoting of identifiers in a language with a lot of keywords makes sense. Consistent case sensitivity or insensitivity of identifiers would also make sense. But making it dependent on the identifier being quoted doesn't look rational.
What am I missing?
Asked by Sergei Morozov
(161 rep)
Dec 25, 2022, 12:39 AM
Last activity: Jan 7, 2023, 10:13 PM
Last activity: Jan 7, 2023, 10:13 PM