SQL Anywhere: Not trimming anything, as SQL Anywhere does not need it but supports distinction-by-blank

[mkarg]

Closes #4521

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

SQL Anywhere does never blank-pad any information provided to Liquibase, so there is no need for trimming.

SQL Anywhere does support duplicate names that differ only by blank padding. For example, one can have all the tables or columns X, X , X and X, and SQL Anywhere correctly can tell which one you want as long as they are correctly double-quoted.

Things to be aware of

N/A

Things to worry about

N/A

Additional Context

N/A

[mkarg]

This PR is in draft mode, because the current solution is not complete. While we do not trim, and while the retrieval of the information from the database correctly results in distinct X, X , X and X instances of CachedRow, the outcome for generateChangelog still is one single consolidated object X. After two days of trying to understand why (and where) this happens, I am running out of time. If someone could chime in and tell me the why and where, I would be happy to finish this PR. Until then, unfortunately I need to invest my time in lower hanging fruits. 😓

[filipelautert]

@mkarg does this PR still a work in progress?

[mkarg]

@filipelautert I am currently busy with other projects, so this PR is suspended until at least end of October. I hope to find the time to continue work then.

[filipelautert]

Thanks for the update @mkarg ! We can wait, no problems.