filter out false positive conflict records in sequentially_slugged #733
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.
The SQL query to return conflicts is picking up additional records where the slug is a substring of a longer slug. For example, the slug "a-string" will return conflicts matching "a-string-1" and "a-string-foo". This was causing ActiveRecord::RecordNotUnique errors.
Rather than implement cross-database regex, this pull request filters out the false positive conflicts after the results are returned.