[
https://issues.apache.org/jira/browse/OFBIZ-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703918#comment-13703918
]
Pierre Smits commented on OFBIZ-5259:
-------------------------------------
I would say this is not a bug, as the import functionality works.
Upgrading of a software system is a project in itself. It must be planned,
orchestrated to ensure a smooth transition with as little disruptions as
possible. Good documentation regarding upgrading helps in that respect.
But if good documentation doesn't exist, a statement in the import screen - to
ensure that the setting in entityengine.xml must be set to 'false' - could be
the next best thing. However, such a statement might also create confusion when
importing data that is not related to an upgrade process.
> entity import dir causes problems because of ecas
> -------------------------------------------------
>
> Key: OFBIZ-5259
> URL: https://issues.apache.org/jira/browse/OFBIZ-5259
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release Branch 12.04
> Environment: All
> Reporter: Skip Dever
> Priority: Minor
>
> If you export all from an existing Ofbiz installation, then import them, lots
> of bad things happen. First, when you import OrderPaymentPreference, an eca
> runs that creates multiple OrderStatus records that did not exist in the
> export. Not too bad except that this eca gets millions of OrderStatusIds
> from the getNextSeqId service which writes updates to SequenceValueItem.
> So, any any eca that runs as a result of the import dir will have the
> SequenceValueItem record overwritten when SequenceValueItem is imported.
> In my view, there should be a bold warning and an option to disable ecas when
> doing this import.
> As was pointed out to me, you can set entity-eca-enabled="false" in
> entityengine.xml before starting ofbiz to do the import and that is why I
> marked this as minor.
--
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
