For some odd reason dbForge refuses to perform a column name change if the new name is just a change in case.
For example, trying to rename a column named ID to id will result in an error "Column id already exists".
Now bear in mind that I am fully aware of the case sensitivity differences between Windows and Linux when it comes to naming however this behavior is completely wrong given that the target MySQL server is running on Linux and case sensitivity is a thing there.
dbForge is the only client that does this. Every other client I've tried performs the renaming without any issues. Even the native Windows mysql CLI client works as expected.
Is there an option in dbForge to disable this behavior because it's clearly something that's done on it's part?
Column already exists
Re: Column already exists
We will investigate this when developing the next product builds.