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

🐛 Bug: no way to save "false" for boolean field #8473

Open
1 task done
masciugo opened this issue May 14, 2024 · 4 comments
Open
1 task done

🐛 Bug: no way to save "false" for boolean field #8473

masciugo opened this issue May 14, 2024 · 4 comments

Comments

@masciugo
Copy link

Please confirm if bug report does NOT exist already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

By providing a checkbox to save a boolean value there's no way to save the False value. If you leave it blank null will be saved. To do that you need to save True and then change it to False

Screenshot 2024-05-14 at 11 48 05

Desired Behavior

I d'like to specify False in the form

Project Details

Node: v20.11.1
Arch: arm64
Platform: linux
Docker: true
RootDB: sqlite3
PackageVersion: 0.207.0

Attachments

No response

@dstala
Copy link
Member

dstala commented May 15, 2024

@masciugo can you confirm if configuring default value (set & clear) helps?

@dstala
Copy link
Member

dstala commented May 15, 2024

With PG as rootDB - didn't see NULL being returned. It's either true or false

@masciugo
Copy link
Author

@masciugo can you confirm if configuring default value (set & clear) helps?

Yes I confirm but the problem is that I don't control the db structure . So I cannot change the default value

@masciugo
Copy link
Author

With PG as rootDB - didn't see NULL being returned. It's either true or false

We target mysql databases

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

No branches or pull requests

2 participants