Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PlanetScale deploy requests fail due to missing unique keys #136

Closed
JoeyMckenzie opened this issue Dec 4, 2023 · 3 comments · Fixed by #142
Closed

PlanetScale deploy requests fail due to missing unique keys #136

JoeyMckenzie opened this issue Dec 4, 2023 · 3 comments · Fixed by #142

Comments

@JoeyMckenzie
Copy link

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.

image

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
@toitzi
Copy link
Contributor

toitzi commented Dec 4, 2023

I think this is the same as #108 maybe you can workarround it till the original issue is resolved / has a solution

@JoeyMckenzie
Copy link
Author

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!

@timacdonald
Copy link
Member

Duplicate of #108

@timacdonald timacdonald marked this as a duplicate of #108 Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants