[
https://issues.apache.org/jira/browse/OFBIZ-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901905#comment-14901905 ]
Paul Foxworthy edited comment on OFBIZ-293 at 9/22/15 4:19 AM:
---------------------------------------------------------------
Please see my discussion in OFBIZ-4602. The canonical XML way to specify a null value is to use the xsi:nil *attribute* (references to XML standards in OFBIZ-4602). The content of an element should be *the data*, and no matter what special value you attempt to reserve (an empty string, the word "null" enclosed in square, curly or angle brackets, etc) something will misinterpret that.
was (Author: paul_foxworthy):
Please see my discussion in OFBIZ-4602. The canonical XML way to specify a null value is to use the xsi:nil *attribute* (references to XML standards in OFBIZ-4602). The content of an element should be *the data*, and no matter what special value you attempt to reserve (an empty string, "[null]", "{null}", etc) something will misinterpret that.
> data import - nulling fields impossible
> ---------------------------------------
>
> Key: OFBIZ-293
> URL:
https://issues.apache.org/jira/browse/OFBIZ-293> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: Marco Risaliti
> Assignee: Jacques Le Roux
> Priority: Minor
> Attachments: OFBIZ-293_set-empty-strings-as-null.patch, ofbiz-293-patch.txt, ofbiz-462-patch.txt
>
>
> It's a copy of the old-jira issue
http://jira.undersunconsulting.com/browse/OFBIZ-462 Tarlika Elisabeth Schmitz
> =================================================
> I am on rev 5274.
> data import from .xml file: empty attributes (e.g. description="") are ignored and the field retains its former value.
> Comment by Chris Juettner [04/Oct/05 01:51 PM]
> This patch comments out the check for null or empty values in the data XML file found by the EntitySaxReader. I also added an additional warning message in case you do not want to persist empty values to the database but still would like to know what happened.
> Comment by Si Chen [04/Oct/05 01:59 PM]
> Chris-
> Just a comment: it's very important that a field in the entity engine is set to null ONLY when the XML file specifically has an empty attribute (ie, description=""). Otherwise, there's a lot of seed data that is in separate XML files, and they could overwrite each other.
> Comment by Chris Juettner [10/Oct/05 11:56 AM] [ Permlink ]
> Si,
> I'm not sure I understand your comment about seed data in seperate XML files overwriting each other. Shouldn't seed data XML files be entity specific? Why would one seed data XML file overwrite another?
> Do you have any comment on what a better solution is for seed data values that could be empty?
> Thanks
> Chris
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)