Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add additional 'idGenMode' mode in SQL FeatureStore mapping configuration #868

Closed
copierrj opened this issue Nov 17, 2017 · 0 comments
Closed

Add additional 'idGenMode' mode in SQL FeatureStore mapping configuration #868

copierrj opened this issue Nov 17, 2017 · 0 comments
Labels
documentation documentation enhancement enhancement or improvement
Milestone
3.4

Comments

@copierrj
Copy link
Member

After discussing the test result of PR #820 (see also: #864) it was decided that we would like to exclude the combination of idGenMode 'GenerateNew' and the newly introduced allowFeatureReferencesToDatastore setting because this combination does not make much sense and might confuse users.

Suggested solution: implementing the idGenMode 'UseExistingAndDatastore' that implies the exiting behavior of 'UseExisting' and allowFeatureReferencesToDatastore set to true.

This new idGenMode should replace the allowFeatureReferencesToDatastore setting.
@tfr42 tfr42 added the enhancement enhancement or improvement label Nov 17, 2017
@tfr42 tfr42 added this to the 3.4 milestone Nov 17, 2017
@tfr42 tfr42 added the documentation documentation label Nov 17, 2017
lgoltz added a commit to lat-lon/deegree3 that referenced this issue Jan 4, 2018
@lgoltz
deegree#868 - replaced WFS configuration option allowFeatureReference…
7aafb7e 
…sToDatastore by a new idGenMode
@lgoltz lgoltz mentioned this issue Jan 4, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation documentation enhancement enhancement or improvement
Projects
None yet
Milestone
3.4
Development

No branches or pull requests
2 participants
@tfr42 @copierrj