Feature request #21907
the "not null" constraint works if the attribute shows literally "NULL" while does not work if the cell is empty
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Vectors | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 29722 |
Description
While I understand the difference between NULL and empty, for the vast majority of users NULL=empty.
Is this the intended behavior or is a bug? if is not considered a bug than I would suggest add a "not empty" option.
History
#1
Updated by Matthias Kuhn over 5 years ago
It was implemented in a database compliant way, so it definitely is "expected behavior".
I think that this could possibly also be improved a lot by changing the behavior of the TextEdit widget which at the moment makes it very easy to get to a "empty" (accepted) value, whereas it should make this very hard and "by default" be NULL on empty.
#2
Updated by Giovanni Manghi over 5 years ago
- Tracker changed from Bug report to Feature request
Hi Matthias, thanks for the feedback
Matthias Kuhn wrote:
It was implemented in a database compliant way, so it definitely is "expected behavior".
ok, this becomes a feature request then
I think that this could possibly also be improved a lot by changing the behavior of the TextEdit widget which at the moment makes it very easy to get to a "empty" (accepted) value, whereas it should make this very hard and "by default" be NULL on empty.
agree, or as I said add a "not empty" option