Renaming a stored property with only a case change results in "column already exists" error

[danchanka]

When attempting to rename a stored property by changing only the case (e.g., renaming serverTimezone to serverTimeZone), an error occurs stating that a column with the specified name already exists. This issue arises because column names in PostgreSQL are case-insensitive by default and are stored in lowercase. Therefore, changing only the case of a column name is interpreted as an attempt to rename the column to an already existing name, causing a conflict.

[danchanka]

Similar problem exists when attempting to rename tables

[danchanka]

It was decided in version 6 to simply check during column/table renaming that the names differ by more than just case. Then, in version 7, the default dbNamingPolicy was updated to enforce lowercase conversion when creating dbName for properties and tables.