Issue 92471 - "Empty Field is NULL" = "No" is not respected for controls unless you touch them
Summary: "Empty Field is NULL" = "No" is not respected for controls unless you touch them
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.4.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-05 12:42 UTC by Frank Schönheit
Modified: 2017-05-20 10:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
document to reproduce the bug case (8.65 KB, application/vnd.sun.xml.base)
2008-08-05 12:43 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2008-08-05 12:42:33 UTC
- open the attached database document
- open the contained form for editing
- put the focus into the "remarks" control, enter some text
- press the "Save Record" button in the toolbar
=> an error message pops up saying that the value for column "name" cannot be NULL

The appearance of this error message is actually wrong. Two setups have been
made to the database which are expected to prevent it:
- The "Form data input checks for required fields" option for the complete
  database has been set to FALSE (see Edit/Database/Advanced)
- The "Empty Field is NULL" property for the edit control which is used to
  input values for the "name" column has been set to "NO".
- (The "name" column is declared to be NOT NULL)

Because of the first option, the form controller is expected to *not* check for
required fields (which works fine, the error message comes from the back-end,
not the front-end).
Because of the second option, the edit control is expected to write an empty
string into the database, not the NULL value. Obviously, this is the point which
does not work.

To verify this: Enter a new record, with "name" *not* being empty. After you
saved this record, change name's edit control to be empty, then save the record
=> Base properly writes the empty string, instead of NULLL
Comment 1 Frank Schönheit 2008-08-05 12:43:28 UTC
Created attachment 55561 [details]
document to reproduce the bug case
Comment 2 Frank Schönheit 2008-09-10 09:56:42 UTC
fixed in CWS dba31c (also for combo boxes, formatted fields, and pattern fields
- they all have the "Empty Field is NULL" property, too).

Added test case to integration.forms.FormControl test, to ensure it doesn't
re-appear.
Comment 3 Frank Schönheit 2008-11-04 19:22:31 UTC
fs->msc: please verify in CWS dba31e
Comment 4 marc.neumann 2008-11-14 12:03:23 UTC
verified in CWS dba31e

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31e
Comment 5 thorsten.ziehm 2009-07-20 14:52:41 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues
Comment 6 thorsten.ziehm 2009-07-20 15:34:55 UTC
Sorry this issue was wrongly closed. This issue will be reopened automatically.
And will be set after that back to fixed/verified.
Comment 7 thorsten.ziehm 2009-07-20 15:39:27 UTC
Set to state 'fixed'.
Comment 8 thorsten.ziehm 2009-07-20 15:43:51 UTC
Set back to state 'verified/fixed'.

Again. Sorry for the mass of mails.