paul-rogers commented on PR #12384: URL: https://github.com/apache/druid/pull/12384#issuecomment-1144325366
The change itself seems fine: creating a constant for the information schema name. +1 (non-binding) on that change. The PR description suggests that this change is made in the context of changing the schema name. The challenge is that, unlike a typical RDBMS, Druid SQL identifiers are case sensitive. So, Druid only knows about this item if the name is upper case: `INFORMATION_SCHEMA`. The reason it is upper-case, it turns out, is that `INFORMATION_SCHEMA` is a [SQL-92](https://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt) feature, and the spec says that the name must be upper case. In a case-insensitive DB, this doesn't matter. But, in Druid, it does. Given that the standard says the name must be upper case, I wonder which DB (or client library) expects the name to be lower case? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
