fix: reduce data dump to only include app specific relations #106
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.
I removed some schemas from the data dump. I only kept the schemas
gaandga_efa. The old dump also containedpostgisandpostgis_rasterrelations and the extenions themselves. That was introduced by #85 but was not caught, because in the local developer docker compose environment the data dump is imported as the database superuserpostgres. But in a cloud (testing) environment where this dump could be used, this is typically not the case. I took the existing dump, imported it, and exported only those schemas with all relations.@sebeweiss is there any specific/necessary data in these relations that the backend (or the demo application) requires? Or can we remove those parts of the dump safely?
I found a bug when asking for Nearest Neighbour with an address given, but could not safely track if that arose from these changes or had been broken before: