Closed
Description
MariaDB 10.2.7 and future releases (5.5, 10.0 and 10.1 branches are not affected) just resolve an old bug in SQL standards implementation and introduce a BC break
Ticket that explains changes https://jira.mariadb.org/browse/MDEV-13132
Ticket that confirms (in comments) only >= v10.2.7 are affected https://jira.mariadb.org/browse/MDEV-13341
Concretely, for Doctrine, schema update just gone crazy and want to update every column with NULL default because 'NULL' is return by MariaDB instead of NULL.
I don't find any other issues… for now.
For the moment, MySQL don't have the same issue.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
Ocramius commentedon Jul 19, 2017
Needs a test case though...
sagaraspl commentedon Aug 24, 2017
Hi @bilhackmac and @Ocramius I also faced the same issue when I updated with MariaDB 10.2.7
belgattitude commentedon Aug 26, 2017
Same issue too.
baumannsven commentedon Aug 26, 2017
I have the same problem.
lcobucci commentedon Aug 26, 2017
@sabzeta @belgattitude @baumannsven as @Ocramius said, please send us a PR with tests. That helps A LOT 😉
sabzeta commentedon Aug 26, 2017
I haven't realy ran into this problem, but it's good to be aware. I'll try to look into it.
Meanwhile, perhaps @sagaraspl could send a PR with tests?
belgattitude commentedon Aug 26, 2017
just published a P/R on doctrine/dbal#2825 with the third approach... Feel free to comment.
mdeboer commentedon Sep 6, 2017
Same problem here, narrowed it down to it being a NULL problem of some sort as removing all nullable relations and fields solved it. That combined with me recently pulling the newest mariadb image for Docker explains it all.
There went another 3/4 hours of my day trying to find an error in my code even though the mapping files validated fine 😭 Using the mysql:5 image now which should fix things, fingers crossed 🤞 .
Hopefully a fix will be merged soon!
51 remaining items