Feature drop oracle locator #154
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
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 3DCityDB requires Oracle at least 19c. With this version, users don't have to choose the
spatialorlocatoroption anymore during the DB setup, because the Oracle Locator Information have been removed and all Oracle Spatial capabilities are available with both Enterprise Edition and Standard Edition 19c. It also means that a full database schema including the relief tables will always be created.Important is that Oracle user (schema) must have the
CREATE TRIGGERprivilege which is required when using GeoRaster. The documentation must be updated.