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

Editing: Saving the value "false" of a boolean does not work with constraint not null #3212

Closed
svaabs opened this issue Dec 5, 2017 · 4 comments
Assignees
Milestone

Comments

@svaabs
Copy link
Contributor

svaabs commented Dec 5, 2017

We do have an editable layer with boolean fields which can not be null. They also do have default values in the database.
In ngeo you can only save a feature of this layer when the boolean is set to true. Otherwise (with false) the field is treated as not set.

Project:

@sbrunner sbrunner added this to the 2.2 milestone Dec 6, 2017
@sbrunner sbrunner added the Ready label Dec 18, 2017
@sbrunner
Copy link
Member

sbrunner commented Dec 20, 2017

I just add a check column on the polygon layer on the demo :-)

@ger-benjamin ger-benjamin added Ongoing and removed Ready labels Jan 3, 2018
@ger-benjamin
Copy link
Member

In ngeo you can only save a feature of this layer when the boolean is set to true. Otherwise (with false) the field is treated as not set.

You mean that you cannot save because it's treated as not filled and so, not valid ? right ?

@svaabs
Copy link
Contributor Author

svaabs commented Jan 3, 2018

Yes, that's it

@ger-benjamin
Copy link
Member

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants