Fix/multientities/rebuild indexes #3663
Merged
Conversation
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
ab051ce to
55be156
Compare
julienbourdeau
approved these changes
May 16, 2025
vincent-pochet
pushed a commit
that referenced
this pull request
May 16, 2025
Because of old invoices that got organization_sequential_id copied into billining_entity_sequential_id, we got not uniq values in billing_entity_sequential_id. For now we're adding this index as not uniq, will add uniqueness after the old invoices are fixed Another solution: add two indexes: before 2025 - all values, after 2025 with uniqueness...
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.
Context
Because of old invoices that got organization_sequential_id copied into billining_entity_sequential_id, we got not uniq values in billing_entity_sequential_id. For now we're adding this index as not uniq, will add uniqueness after the old invoices are fixed
Another solution: add two indexes: before 2025 - all values, after 2025 with uniqueness...