You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using PlanetScale, I was unable to apply migrations to the production branch due to missing unique keys. Was able workaround this by adding a $table->bigIncrements('id') to each pulse table definition, though I'm not sure if that's intended in the case these are meant to be key-less tables or identified by the various indexes on each table.
I'm fairly new to Laravel, so I'm not too sure if this is really a pressing issue. Applying the keys manually seems to fix the issue.
Steps To Reproduce
Create new Laravel application use the mysql connector
Connect to PlanetScale, create a dev branch off main
Apply migrations locally
Create a deploy request to merge dev changes into main
The text was updated successfully, but these errors were encountered:
Figured that might be the case. Easy enough to work around in the case of PlanetScale, working as expected with just those few changes. Thank you for taking a look!
Pulse Version
1.0@beta
Laravel Version
10.10
PHP Version
8.3
Database Driver & Version
No response
Description
Using PlanetScale, I was unable to apply migrations to the production branch due to missing unique keys. Was able workaround this by adding a
$table->bigIncrements('id')
to each pulse table definition, though I'm not sure if that's intended in the case these are meant to be key-less tables or identified by the various indexes on each table.I'm fairly new to Laravel, so I'm not too sure if this is really a pressing issue. Applying the keys manually seems to fix the issue.
Steps To Reproduce
mysql
connectordev
branch offmain
dev
changes intomain
The text was updated successfully, but these errors were encountered: