You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Sharan Foga (JIRA)" <ji...@apache.org> on 2015/02/21 08:39:15 UTC

[jira] [Updated] (OFBIZ-5259) entity import dir causes problems because of ecas

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

Sharan Foga updated OFBIZ-5259:
-------------------------------
    Sprint: Bug Crush Event - 21/2/2015

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)