[
https://issues.apache.org/jira/browse/OFBIZ-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin updated OFBIZ-4949:
---------------------------------
Attachment: OFBIZ-4949-NMA.patch
In view of the comments, we can consider the #3 solution as consensu :)
I submitted a new patch with this solution and add a example on
specialpurpose/example/data/ExampleDemoData.xml.
If you load data with verbose debug you see some lines like " Detail created :
1, skipped : 3, updated : 42, replaced : 1, deleted : 0"
After a first review, I will create junit test.
Warn, if you load specialpurpose/example/data/ExampleDemoData.xml one more, the
result given by detail line will be different because the transaction commit
works by step with size 100.
> Add a new attribute for entity-engine-xml tag, nullify-absent-fields
> --------------------------------------------------------------------
>
> Key: OFBIZ-4949
> URL: https://issues.apache.org/jira/browse/OFBIZ-4949
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Olivier Heintz
> Priority: Minor
> Attachments: OFBIZ-4949-NMA.patch, OFBIZ-4949-NMA.patch,
> OFBIZ-4949.patch, OFBIZ-4949.patch, OFBIZ-4949.patch
>
>
> This enhancement is useful when a entity is load by reader (ex: seed) and
> sometime, it could be modify in data file. If a field is change from a value
> to null, currently this modification will not be done in the next load.
> When you are first importing new data, quite naturally all fields other than
> those specified in the file will be null. If, however, you're updating
> existing data, you might want any field not specified in the file to retain
> its current value, or you might want the contents of the file to specify
> everything about a record, in other words "take this data and null out the
> rest". The alternative to set-other-fields-to-null (or whatever else we
> might call it) would be a huge number of attribute="" in the file.
> For portletWidget, entity PortalPortal have a lot of field with potential
> default value, so sometime, first release use some field and when it's
> reviewed and corrected, some field are changed to null to use the default
> value (to follow best practice).
> This enhancement will be very useful for portletData file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
