Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
SQLSTATE[42000]: Syntax error or access violation: 1171 All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead Proudly built byCommerce Guys. So there error doesn't state which table the error is for. This error happens during new profile installation: http://demo.dev/install.php?profile=commerce_kickstart&welcome=done&loca...
Comment | File | Size | Author |
---|---|---|---|
#4 | message-mysql57_compatibility-2629474-4.patch | 372 bytes | KevinVanRansbeeck |
Comments
Comment #2
si_odong CreditAttribution: si_odong as a volunteer commentedI got the same error and found that it caused by message_schema in message.install, modules that needed in commerce_kickstart module. If you insist to install on mysql 5.7>, simply add "'not null' => TRUE," in "mid" field (line 194) of message.install, re-run clean installation profile and it will installed flawlessly. But, it might be better to let message module or commerce_kickstart distro developer patch this issue. Hope it helps you.
Comment #3
mglamanComment shows there's an "issue" with Message install schema. Albeit it's for MySQL 5.7, but there's a solution provided that seems to fix it.
Patch can be made in Message queue, with a patch to use the patch in CK quue.
Comment #4
KevinVanRansbeeck CreditAttribution: KevinVanRansbeeck at AmeXio commentedFixed in development branch.
For the sake of make files I created a patch which can be included for stable versions.
Comment #5
mglamanKevinVanRansbeeck thanks for info! I'll move this back to CK2 queue then, to use your patch. I'll write CK2 patch and give you authorship
Comment #6
mglamanPR, waiting for tests. I'd assume they pass! https://github.com/commerceguys/commerce_kickstart/pull/173
Comment #7
mglamanComment #9
mglamanComment #11
KevinVanRansbeeck CreditAttribution: KevinVanRansbeeck at AmeXio commented@mglaman, the patch fixes this for current version of message, but this needs fixing in the message project itself
Should I create a new ticket there, or can we move this one again so it can get fixed in message 1.12?
Comment #12
mglamanIn #4 you said it's fixed in their -dev branch, and I confirmed. We'd just need them to tag a release with that in it. Or if the release does have it, upgrade Message.