1.5 migration that add creation/modification timestamps results in zeros
arteymix opened this issue · 1 comments
arteymix commented
These zeroes are not allowed when loading entities with Hibernate
- add a migration to mitigate existing zeroes by converting them to NULLs
- ensure that the replacement migration uses NULL for default values
The same migration fails with MySQL 5.7 because it defines more than one timestamp column for various tables and it only allow one with CURRENT_TIMESTAMP as default.