Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-293

data import - nulling fields impossible

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug Crush Event - 21/2/2015, Community Day 3 - 2015

    Description

      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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jleroux Jacques Le Roux
            risalitm Marco Risaliti
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprints:
                Bug Crush Event - 21/2/2015 ended 26/Feb/15
                Community Day 3 - 2015 ended 22/Sep/15
                View on Board

                Slack

                  Issue deployment