-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🗃️(api) make location coordinates unique #330
Merged
jmaupetit
merged 2 commits into
main
from
api-remove-localisation-adresse-field-uniqueness-alt
Jan 17, 2025
Merged
🗃️(api) make location coordinates unique #330
jmaupetit
merged 2 commits into
main
from
api-remove-localisation-adresse-field-uniqueness-alt
Jan 17, 2025
+94
−3
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
jmaupetit
added
WIP
schema
Discussions around data schemas
API
Item related to the API service
improvement
labels
Jan 10, 2025
jmaupetit
force-pushed
the
api-remove-localisation-adresse-field-uniqueness-alt
branch
from
January 13, 2025 17:59
590af3b
to
e9e227e
Compare
jmaupetit
force-pushed
the
api-remove-localisation-adresse-field-uniqueness-alt
branch
2 times, most recently
from
January 14, 2025 10:37
3d32594
to
0d5a2c6
Compare
2 tasks
Current benchmark
Comparison with the latest previous benchmark
|
Staging database duplicated |
Should be ok to merge now! |
jmaupetit
force-pushed
the
api-remove-localisation-adresse-field-uniqueness-alt
branch
from
January 17, 2025 15:18
0d5a2c6
to
9ba6d37
Compare
Instead of having a unique Localisation.adresse_station field, let's be more pedantic and refuse to have two locations with the same coordinates.
Yeah, it disturbed me.
jmaupetit
force-pushed
the
api-remove-localisation-adresse-field-uniqueness-alt
branch
from
January 17, 2025 15:24
9ba6d37
to
86ec927
Compare
Current benchmark
Comparison with the latest previous benchmark
|
jmaupetit
deleted the
api-remove-localisation-adresse-field-uniqueness-alt
branch
January 17, 2025 15:33
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Purpose
Instead of having a unique
Localisation.adresse_station
field, let's be more pedantic and refuse to have two locations with the same coordinates.Proposal
localisation_coordonneesXY_key
constraint to the Localisation tableRemark
This is an alternative implementation to fix issue #309 (see also #329).