Added calculation of the bounding box across multiple geometry columns for PostgreSQL (3.5) #1729
+111
−36
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
julianzz98
changed the title
|
Since the interface of SQLDialect has been changed by adding new methods and an implementation is provided for PostGIS only it requires further testing if this change affects the other dialects. |
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.
With this PR, the functionality of deegree was enhanced so the bounding box (BBOX) can be calculated across multiple geometry columns (PostgreSQL) when the REST API request
/deegree-webservices/config/update/bboxcacheis used.Prior to the change the functionality behind the mentioned REST API request would only consider the first fitting geometry column for its calculation, even if it was supposedly empty.