add fix for mariadb virtual column creation#2158
add fix for mariadb virtual column creation#2158oskarkregar wants to merge 2 commits intocakephp:0.xfrom
Conversation
|
I'm not sure if it's overly reasonable to completely break the Maybe the check should rather look for SQL that is incompatible with In any case, this should have tests. Since existing tests didn't break, there seems to already be missing coverage. |
|
We don't currently test against mariadb, so we'd need to wire that up before we could have a good test for this. MySQL does happily allow |
|
It could then be fixed with option to explicitly suppress |
|
Is there an argument to say that adding options to a Literal column type is unnecessary? By definition we are manually specifying the column and allowing options just adds complexity. Then we might do; |
|
@ndm2 So you think we shouldn't merge this? |
|
@dereuromark Not in this state, no. IMHO there should either be an option to exclude |
When using virtual column definition with
Literalclass, migration fails with SQL syntax error on MariaDB asNOT NULLorNULLare not allowed at the end of column definition. Below is the link to an issue.Fixes #2157