Change C_DV_ORDINAL to use CODE_PHRASE rather than DV_CODED_TEXT
Raise
Analysis
Raise
Analysis
Description
Activity
Show:
Sebastian Garde March 6, 2024 at 3:01 PM
+1 to close.
Ian McNicoll March 6, 2024 at 2:58 PM
Agree and Iād close this - ancient history (2012)
Severin Kohler March 6, 2024 at 2:39 PMEdited
Hm, i personally don't like that since that introduces redundancy/inconsistency to the model, cause in the end you recreate a DV_CODED_TEXT.
Besides that it has effects on the current implementations.
Having nulls as a workaround is acceptable, but not optimal.
Not worth the cost creating something inconsistent, if the DV_CODED_TEXT is the correct use here.
Details
Details
Created May 21, 2012 at 4:09 PM
Updated March 6, 2024 at 3:01 PM
Currently C_DV_ORDINAL is simply represented as a list of DV_ORDINAL, which in turn makes use of DV_CODED_TEXT to represent symbol and includes a mandatory value attribute, inherited from DV_TEXT.
This is causing java xml outputs to fail because the mandatory value attribute is not populated as part of a constraint. The .Net XML outputs an empty <value/> element to work around the issue.
A better solution might be to for C_DV_ORDINAL to define its constraints as a list of a new type that contains a value + CODE_PHRASE