Rearranging and fixing problems within create_featurestore method and adding new method "edit_featuretype" #60
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
… method edit_featuretype
…ers; added new method edit_featuretype;
JLoos92
changed the title
|
Thank you very much for this PR. I will add this code in the next release. |
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.
I was able to fix the problem with a couple of connection parameter settings (e.g. expose primary keys) in the create_featurestore method. It was more like a .xml format problem. However, I added the missing default parameters for the connection pool.
Furthermore, I added a method called "edit_featuretype" to change name and title of the published feature.
I tested this version locally within geoserver applications and it worked very well.
Cheers, Julius