Feature request: Change interpretation of empty string depending on NOT NULL flag
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Current behaviour:
Many of the text fields in my day-to-day database work are set to NOT NULL. If I erase the contents of a text string in the table row view, or in the detail sidebar, my intention is to insert the empty string into this field, but Postico is assuming I want to enter NULL and this triggers a validation error, meaning I cannot save the row. I then have to go back and explicitly choose "Empty String" from the dropdown menu next to the field.
Proposed behaviour:
If a field is marked NOT NULL, then when the user presses Enter in a text field containing no text, Postico should insert the empty string into the field.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the behavior in the table row view and detail sidebar by clearing a text field marked NOT NULL and pressing Enter. Trace the UI path for the field value and validation, then verify that saving inserts an empty string for NOT NULL fields while the existing explicit NULL and Empty String choices remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100