arrivals_departures/connections: move id column into separate view #66
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.
Currently, queries on
arrivals_departures
&connections
are slow as soon as there arefrequencies
-based rows in there. This is because thefrequencies_it
– which is needed forarrival_departure_id
/connection_id
– calculation uses arow_number()
over aPARTITION BY
.This PR
arrivals_departures_with_ids
/connections_with_ids
;arrival_departure_by_arrival_departure_id
/connection_by_connection_id
to use the new views;