This repository has been archived by the owner on Oct 5, 2024. It is now read-only.
Handle two databases #500
Merged
Handle two databases #500
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
… list instead of a huge string
… is now an entry in a list. Also handle queries returning no data
…he data between two databases, one for raw data, the other for underpass
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This completes the previous changes so Underpass works with two databases. One is for the Underpass changesets and validation. The other is for raw OSM data. Previously all the SQL queries were a huge string. This changes the dataflow to use a vector of SQL strings instead, so each query can go to the correct database.