Closed hagealex closed 3 months ago
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication mediums:
backpack-for-laravel
tag;Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot
Nevermind. After an Update of my Laravel to the current 10.* release the error didn't occur anymore.
Bug report
What I did:
I setup the permissionmanager according to the documentation. On my local Laravel Homestead environment it worked. While trying to deploy on my hoster I run in the below mentioned error.
After enabling
sql_require_primary_key
on my local mysql I face the same error.For me it looks like there is something not working with the composite primary keys. But I'm no mysql expert so I can just guess.
Did some face a similar issue and knows how to fix it?
Note: I can't turn off the
sql_require_primary_key
on my hoster.What I expected to happen:
The migrations runs through succesfully.
What happened:
What I've already tried to fix it:
Backpack, Laravel, PHP, DB version:
Backpack 6.4.2 Laravel 10.32.1 DB: mysql 8.0.35