CV2-4600 alter migrations given preexisting indices#422
Open
CV2-4600 alter migrations given preexisting indices#422
Conversation
|
Code Climate has analyzed commit 5af9fb6 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 80.9% (0.0% change). View more on Code Climate. |
skyemeedan
approved these changes
Jun 4, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Minor oversight from original implementation of CV2-4600 - we already had these GIN indices - we just need the others. The migrations failed, so no changes were applied, so merely editing this existing migration should do the trick.
Reference: CV2-4600
How has this been tested?
Not tested locally, tested in prod, lol
Have you considered secure coding practices when writing this code?
None