MySQL table identifiers are usually case sensitive on non-Windows systems. If your code has mixed case table names, but the database has all lower case table names, then my guess is that you used to use a MySQL server where lower case table names were turned on and you’re migrating to a new one that doesn’t have the same option set?
(Or if you’re using something like AWS RDS then you’d need to set that in an Option Group since you don’t have direct access to the config file itself).
That did it! Thank you very much, and for the quick reply!
This codebase is over 10 years old, so 10 years ago I probably wanted camelCase table names for readability. I’ve migrated this code/database a few times over the years, and with ColdFusion being case-insensitive I guess I’ve never had this problem, and always ran CF on Windows – or maybe I had to fix this years ago and don’t remember.
This fix actually fixed another issue where it said something like KEY NOT FOUND when doing a simple <cfoutput>#ucase(BRAND_DOMAIN)#</cfoutput>. I tried to change it to brand_domain, but that didn’t work.
Now I just have to figure out how to keep the machine from crashing.
I’m using Amazon Lightsail w/ Ubuntu OS only. Installed Lucee & MySQL manually. I’m only testing so I started with a 512RAM and have since upgraded to a 1GB RAM server. Maybe I need to move to 2 or 4GB, and probably will once I’m ready for production.
The SQL specification actually calls for case-insensitivity, and most DBMSs will automatically lowercase or UPPERCASE your names for you unless you quote them.
I’m actually migrating a database from SQL Server, which maintains the original CaSe, to Postgres, which follows the specification and does not, resulting in the less readable camelcase names, so I am converting the camelCase tables to snake_case. I posted about it recently at https://lucee.daemonite.io/t/rebind-jquery-tablesorter/2711/14?u=21solutions