XF 2.0 Breaking changes in 2.0.10

S Thomas

Well-known member
Just was confronted with this:
Code:
XF\Db\InvalidQueryException: MySQL query error [1171]: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead in src/XF/Db/AbstractStatement.php at line 212
While this itself makes total sense, I haven't seen that on 2.0.7. Are there more breaking changes in 2.0.7+ which would cause backwards incompatibility?
 
That's a MySQL error, so it may not be a breaking change in 2.0.10, but a bad query. Can you provide the code in question? If it worked in 2.0.7 and didn't in 2.0.10, that would point more to a bug than an intentional change.
 
Thanks Mike, indeed a MySQL error. The client has MySQL 5.7.23 installed, MySQL 5.7 removed null values for primary keys.
 
Top Bottom