Fix "unknown column" exception #943
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When custom `slug_column` is used along with `history` and `sequentially_slugged` modules, wrong query was being formed on `Slug` model. Query being made - `select friendly_id_slugs.strange name from artists` Query which should be made - `select friendly_id_slugs.slug from artists` This commit fixes it to use default `slug` column in such case.
parndt
reviewed
Jun 10, 2020
parndt
reviewed
Jun 10, 2020
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
A method name with `and` is usually an indicator that it does too much
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When custom
slug_columnis used along withhistoryandsequentially_sluggedmodules, wrong query was being formed onSlugmodel.
Query being made -
select friendly_id_slugs."strange name" from artistsQuery which should be made -
select friendly_id_slugs.slug from artistsThis commit fixes it to use default
slugcolumn in such case.