Issue 75802

Summary: Forms should not use NOT NULL attribute to return Required message box
Product: Base Reporter: odaata <mike.olson3>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Details for Issue 75801 none

Description odaata 2007-03-28 06:49:29 UTC
When designing databases, I try to make sure text fields never have a NULL
value, so code and queries are much less complicated and less error prone, so if
a field is optional for the user, I set it to NOT NULL with a DEFAULT ''. This
does not work in Base however, because the forms will not allow the user to
leave a field blank if it is a NOT NULL field. The only workaround for this is
to remove the NOT NULL constraint, but that opens your data up to possible NULL
values - see the issue on the 'Empty String is NULL' property (75799).

When adding new records, Base should only submit fields that the user has
changed. Then the DB will fill in any defaults or return an error if a field is
required. You could also allow people to set a default of '' in the metadata for
the table (Edit table view) and then use that for updates as well.

This is a fundamental requirement for DBs in general and MS Access handles this
really well (with a nice description of it in their help file).

Thanks,
Mike Olson
Comment 1 odaata 2007-03-30 03:47:51 UTC
Created attachment 44033 [details]
Details for Issue 75801
Comment 2 odaata 2007-03-30 03:48:54 UTC
Don't know how I did it, but I attached the file for the previous Issue to this
one - please ignore it.
Comment 3 christoph.lukasiak 2008-05-07 12:12:46 UTC
confirm
Comment 4 christoph.lukasiak 2008-05-07 12:13:25 UTC
send further to the requirements team