Fix: Integrity constraint violation: 1052 Column 'id' in where clause is ambiguous #3772
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
Analog to #3696, changed 'id' to 'groups.id' to avoid
Column 'id' in where clause is ambiguous
error.This error normally doesn't occur, but if an extension adds an
id
column to thegroup_user
table, then this error would occur.(Adding that column helps when one wants to
chunkById()
on thegroup_user
model)Reviewers should focus on:
Nothing is broken by this minor change.
Necessity
Confirmed
composer test
).