Add stop_place_newest_version metadata #227
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
HenrikHartiala
force-pushed
the
add-stop-place-newest-version-metadata
branch
2 times, most recently
from
55dfe1e
to
d1fbf14
Compare
Add the necessary metadata to track stop_place_newest_version which is a view that only has the newest versions of a stop (distincted by netex_id). Also add the necessary relationships, a remote relationship to tiamat API stop place and remote relationship to scheduled_stop_point. We might have use for both, or only one of these remote relationships, but should be no harm in adding both. Resolves https://dev.azure.com/hslfi/JORE%204.0/_workitems/edit/35459
HenrikHartiala
force-pushed
the
add-stop-place-newest-version-metadata
branch
from
d1fbf14
to
ad9a9cc
Compare
culka
approved these changes
Apr 22, 2024
There was a problem hiding this comment.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @HenrikHartiala)
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.
Add the necessary metadata to track stop_place_newest_version which
is a view that only has the newest versions of a stop (distincted by netex_id).
Also add the necessary relationships, a remote relationship to tiamat API
stop place and remote relationship to scheduled_stop_point. We might have
use for both, or only one of these remote relationships, but should be
no harm in adding both.
Resolves https://dev.azure.com/hslfi/JORE%204.0/_workitems/edit/35459
This change is