Our main database for our organization is Oracle-based and we have tons of complicated queries already created for it. I’ve recently spun back up a MemSQL environment for me to copy some of our Oracle tables into and we had one of our Researchers trying to run an existing query in MemSQL and one of the issues they ran into was that they had typed in their table names in lowercase rather than in uppercase which MemSQL expects.
I ran a quick Google search about the issue and came back with the following suggestion which mentions creating a VIEW for each table name with the lowercase (or other mixed-case) variation you might need to support:
That’s not a bad solution to implement, however I am wondering about why this has to be an issue in the first place?
Particularly because it seems to be that the SQL Parser for MemSQL really only cares about this requirement in the FROM clause of the query being provided because in the example I helped my colleague out with, I only made the adjustments there and was able to get the query working (elsewhere in the query’s SELECT and WHERE/AND, GROUP BY, and ORDER BY clauses the field names were provided in mixed case which MemSQL had no problems in interpreting/processing correctly).