You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Dimitri Unruh (JIRA)" <ji...@apache.org> on 2010/02/10 23:28:32 UTC

[jira] Updated: (OFBIZ-3421) Allow data load to support explicit "null" values for entity update

     [ https://issues.apache.org/jira/browse/OFBIZ-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dimitri Unruh updated OFBIZ-3421:
---------------------------------

    Attachment: ofbiz.patch

Jacques,

maybe this patch could do this.

Dimitri Unruh

> Allow data load to support explicit "null" values for entity update
> -------------------------------------------------------------------
>
>                 Key: OFBIZ-3421
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3421
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Bob Morley
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: OFBIZ-3421_AllowNullInDataLoad.patch, ofbiz.patch
>
>
> We required the ability to be able to have the data load update existing entities with a null value on existing records.  The reason for this was that we had a site in production where a product subscription resource was set to only allow 1 use.  We wanted to change this record to unlimited uses, so we wanted to have the entity change its value back to "null" in the database.  This change may be a bit of a hack; as it looks for "null" specifically in the data load file and then replaces that on the newly loaded entity with null to ensure backwards compatibility.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.