Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impact
Description
Added Tibero database.
Tmax Tibero is a well known RDBMS in South Korea. The syntax of Tibero is similar to Oracle's, but there are some differences.
Fixes #2226
https://forum.liquibase.org/t/liquidibase-tibero-combination/9046
https://forum.liquibase.org/t/create-table-databasechangelock-fails-on-tibero-db/6188
There is no BOOLEAN type, and DATETIME type in Tibero, so it is not possible to use liquibase.database.core.OracleDatabase as a databaseClass. That is why I decided to add TiberoDatabase class which extends AbstractJdbcDatabase class.
Things to be aware of
Things to worry about
I have implemented the bare minimum to enable Tibero DB users to utilize Liquibase. I have checked that it works correctly when the changelog file is in SQL format. However, I have not tested whether it can utilize the features specific to the Tibero database itself and the various abstraction functionalities of Liquibase. It seems that these features will need to be added in the future.
Additional Context