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

[8.x] Shouldn't the migrations use bigIncrements and indexes on relationships? #1169

Merged
merged 5 commits into from
Jan 21, 2020
Merged

Conversation

KieronWiltshire
Copy link
Contributor

@KieronWiltshire KieronWiltshire commented Jan 21, 2020

I was looking through the migrations and saw that some of them seem pretty dated and don't use bigIncrements and indexes on certain possible relationships like the user_id field here.

@driesvints
Copy link
Member

Have you tried these changes on all four supported DB drivers? Sqlite, MySQL, PostGres & SQL Srv?

@KieronWiltshire
Copy link
Contributor Author

@driesvints I have only tested this with MySQL, I was under the assumption that the point behind the Schema interface is that it abstracts the four supported drivers away

@driesvints
Copy link
Member

@KieronWiltshire have you checked into how the cascading deletes affect the underlying repository code? I suspect atm the code within Passport itself is currently handling the deletion of related records etc.

@KieronWiltshire
Copy link
Contributor Author

@driesvints I didn't see the point as I couldn't find any use cases as to where it would be damaging, for example... if a client is deleted, shouldn't access tokens etc be deleted along with? there would be no reason to keep them?

@driesvints driesvints changed the title Shouldn't the migrations use bigIncrements and indexes on relationships? [8.x] Shouldn't the migrations use bigIncrements and indexes on relationships? Jan 21, 2020
@taylorotwell taylorotwell merged commit 128f99c into laravel:8.x Jan 21, 2020
@clemblanco
Copy link
Contributor

Same question for oauth_personal_access_clients.client_id?

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 this pull request may close these issues.

None yet

5 participants