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.

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

Enforce feature IDs unicity at database level #368

Open
claustres opened this issue Jul 8, 2024 · 0 comments
Open

Enforce feature IDs unicity at database level #368

claustres opened this issue Jul 8, 2024 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@claustres
Copy link
Member

Although a unique featureId can be specified on layers targeting the generic features service there is no enforcement of the unicity rule at the database level. It is because this service can be used by different layers and we do not know the feature IDs upfront to create the indices in the model file. We should add/remove indices dynamically based on all layers using the service.

@claustres claustres added bug Something isn't working enhancement New feature or request labels Jul 8, 2024
@claustres claustres moved this to Bugs in Kano Roadmap Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: Bugs
Development

No branches or pull requests

1 participant