You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Marco Risaliti (JIRA)" <ji...@apache.org> on 2006/09/14 21:58:26 UTC
[jira] Created: (OFBIZ-293) data import - nulling fields impossible
data import - nulling fields impossible
---------------------------------------
Key: OFBIZ-293
URL: http://issues.apache.org/jira/browse/OFBIZ-293
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Components: framework
Affects Versions: SVN trunk
Reporter: Marco Risaliti
I am on rev 5274.
data import from .xml file: empty attributes (e.g. description="") are ignored and the field retains its former value.
All Comments Work Log Change History Sort Order:
Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
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] [ Permlink ]
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.
Si
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
Comment by Marco Risaliti [14/Sep/06 01:58 AM] [ Permlink ]
Can I move it ?
Thanks
Marco
It's a copy of the old-jira issue OFBIZ-462
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-293) data import - nulling fields impossible
Posted by "Marco Risaliti (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-293?page=all ]
Marco Risaliti updated OFBIZ-293:
---------------------------------
Attachment: ofbiz-462-patch.txt
> data import - nulling fields impossible
> ---------------------------------------
>
> Key: OFBIZ-293
> URL: http://issues.apache.org/jira/browse/OFBIZ-293
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Marco Risaliti
> Attachments: ofbiz-462-patch.txt
>
>
> I am on rev 5274.
> data import from .xml file: empty attributes (e.g. description="") are ignored and the field retains its former value.
>
>
> All Comments Work Log Change History Sort Order:
> Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
> 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] [ Permlink ]
> 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.
> Si
> 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
> Comment by Marco Risaliti [14/Sep/06 01:58 AM] [ Permlink ]
> Can I move it ?
> Thanks
> Marco
> It's a copy of the old-jira issue OFBIZ-462
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-293) data import - nulling fields impossible
Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-293?page=all ]
Jacopo Cappellato updated OFBIZ-293:
------------------------------------
Priority: Minor (was: Major)
> data import - nulling fields impossible
> ---------------------------------------
>
> Key: OFBIZ-293
> URL: http://issues.apache.org/jira/browse/OFBIZ-293
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Marco Risaliti
> Priority: Minor
> Attachments: ofbiz-462-patch.txt
>
>
> I am on rev 5274.
> data import from .xml file: empty attributes (e.g. description="") are ignored and the field retains its former value.
>
>
> All Comments Work Log Change History Sort Order:
> Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
> 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] [ Permlink ]
> 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.
> Si
> 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
> Comment by Marco Risaliti [14/Sep/06 01:58 AM] [ Permlink ]
> Can I move it ?
> Thanks
> Marco
> It's a copy of the old-jira issue OFBIZ-462
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-293) data import - nulling fields impossible
Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-293?page=all ]
Jacopo Cappellato updated OFBIZ-293:
------------------------------------
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.
All Comments Work Log Change History Sort Order:
Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
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] [ Permlink ]
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.
Si
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
was:
I am on rev 5274.
data import from .xml file: empty attributes (e.g. description="") are ignored and the field retains its former value.
All Comments Work Log Change History Sort Order:
Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
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] [ Permlink ]
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.
Si
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
Comment by Marco Risaliti [14/Sep/06 01:58 AM] [ Permlink ]
Can I move it ?
Thanks
Marco
It's a copy of the old-jira issue OFBIZ-462
> data import - nulling fields impossible
> ---------------------------------------
>
> Key: OFBIZ-293
> URL: http://issues.apache.org/jira/browse/OFBIZ-293
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Marco Risaliti
> Priority: Minor
> Attachments: 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.
>
>
> All Comments Work Log Change History Sort Order:
> Comment by Chris Juettner [04/Oct/05 01:51 PM] [ Permlink ]
> 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] [ Permlink ]
> 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.
> Si
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira