Fixed Liquibase properties which where not compatible with MySQL #3271
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.
This PR fixes Liquibase properties for MySQL which are currently not compatible
Related Issue
None
Description of the solution adopted
For some reasons MySQL database was replacing the
CURRENT_TIMESTAMP(3)
invocation withNOW()
which makes defintions like:created_on TIMESTAMP(3) DEFAULT NOW()
result the following error:
Replacing
CURRENT_TIMESTAMP(3)
withNOW(3)
makes everything work as expected in MySQL.Screenshots
None
Any side note on the changes made
Since H2 works fine with
NOW()
,CURRENT_TIMESTAMP()
andCURRENT_TIMESTAMP(3)
it has been left usingCURRENT_TIMESTAMP(3)