Mariadb migration can not create nullable timestamp column #14088
Labels
dialect: mariadb
For issues and PRs. Things that involve MariaDB (and do not involve all dialects).
type: bug
Issue Creation Checklist
[x] I have read the contribution guidelines
Bug Description
Although for other datatypes, such a varchar, the default for MariaDb is Allow Null is true, but for timestamps it is false and it is handled differently, see the documentation and more docs here But is says there
One should therefore be able to specify when creating a timestamp column that it should be nullable, like this.
What do you expect to happen?
That should run the following query: (Note the
NULL
)What is actually happening?
It is running this instead: (Note the
NULL
is missing)Additional context
This is a problem, because I want to add this field to an existing table, and if I don't make it nullable, it will insert the current timestamp into each existing row, (as mentioned in documentation linked above).
I can do it like this, but I believe it is still a bug.
Environment
Bug Report Checklist
How does this problem relate to dialects?
Would you be willing to resolve this issue by submitting a Pull Request?
The text was updated successfully, but these errors were encountered: