0007346: Solve inconsistency: nullable db-columns which have mandatory to Y in the Application Dictionary

Description

In the 2.60 clean up project the following inconsistency needs to be solved:

There is a validate.database task which checks the database for inconsistencies. One of the checks is for nullable database columns which are defined as mandatory in the Application Dictionary.

The check is there, but disabled in the org.openbravo.service.system.DatabaseValidator. See these lines:
    // disabled this check, will be done in 2.60
    if (false) {
      if (property != null && property.isMandatory() && !dbColumn.isRequired()) {
        result.addWarning(SystemValidationType.MANDATORY_IN_AD_NULLABLE_IN_DB, "Column "
            + dbTable.getName() + "." + dbColumn.getName()
            + " is not-required (null-allowed) but in the Application Dictonary"
            + " it is set as mandatory");
      }
    }

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

blocks

feature request

0007236

acknowledged

shuehner

Tracking issue: Cleanup for 3.00

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2009-02-03 17:09	mtaal	New Issue
2009-02-03 17:09	mtaal	Assigned To	=> shuehner
2009-02-03 17:09	mtaal	sf_bug_id	0 => 2561227
2009-02-03 17:09	mtaal	Regression testing	=> No
2009-02-03 17:09	mtaal	Relationship added	depends on 0007236
2009-02-03 18:08	shuehner	Relationship deleted	depends on 0007236
2009-02-03 18:08	shuehner	Relationship added	blocks 0007236
2011-05-25 13:12	dmitry_mezentsev	Priority	normal => high
2011-06-02 10:54	dmitry_mezentsev	Target Version	3.0MP0 => 3.0MP1
2011-06-22 19:26	dmitry_mezentsev	Target Version	3.0MP1 => 3.0MP2
2011-06-22 20:05	shuehner	Target Version	3.0MP2 =>
2012-02-20 11:25	shuehner	Assigned To	shuehner => alostale
2017-04-10 14:38	alostale	Assigned To	alostale => platform
2022-02-01 08:08	alostale	Assigned To	platform => Triage Platform Base