Skip to content

Conversation

davel
Copy link

@davel davel commented Jan 18, 2021

This patch handles a behaviour change preventing schemas using DEFAULT current_timestamp() from being correctly imported from MariaDB.

MariaDB made a change about five years ago which causes it to say current_timestamp() rather than current_timestamp when outputting schema. This was quite deliberate, see https://jira.mariadb.org/browse/MDEV-13377 and MariaDB/server@a411d7f

This builds on @mrenvoize's unmerged #23 .

mrenvoize and others added 3 commits April 3, 2020 08:47
At some point, MariaDB started outputing 'current_timestamp()' in the
default field when DESCRIBE is called on the table. This is a change
from 'CURRENT_TIMESTAMP' in mysql and older versions of mariadb.  As
such, our equality match started to fail and resulting schema dumps
produced `current_timestamp()` instead of `\"current_timestamp"`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants