This does not break functionality

This does not break functionality, but for legacy environments it becomes confusing, especially for teams working with older COBOL/ERP systems where uppercase naming conventions are heavily used.

Would it be possible to add an option such as:

“Preserve original identifier case” “Display object names using metadata case”

This would help environments that rely on traditional uppercase naming conventions.

Thank you for the excellent software and support.

Sorry, what is the situation you describe here? Is it the SQL editor and you mean column names taken from the completion proposal? These should be preserved as they're defined in the table (see the "Column 1" column name):

Heidi forces the table name to be in lowercase. I've attached a screenshot.

I have configured MariaDB on Windows with lower-case-table-names=2 in my.ini, so I can create tables which keep the written case. But this is a server configuration. You might have done the same, or you run a Linux server, however.

Now HeidiSQL does not force the name to lowercase when using the completion proposal. You may write the lowercase name by hand, but that is then up to you. Here's a recording of the completion proposal.

Hi,

Defaults for lower-case-table-names are 0 and it does not seem to force any case on a Linux server either, running MariaDB 10.11.14 on Linux here. (the sample query was using the completion editor)

Regards