[
https://issues.apache.org/jira/browse/OFBIZ-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475591
]
Chris Howe commented on OFBIZ-757:
----------------------------------
An option that would have helped initially is when you export data that it
writes the records sorted by created date instead of alphanumerically by the
first field in the definition.
is there a way to suspend the referential integrity check until after the file
is loaded? then roll back if it fails instead of checking each line. I'm
thinking that would be more of a database specific thing.
I'm migrating from MySql to postrgres and it's proving quite difficult with the
denormalized data being stuck onto the end of entities the way they are...(eg
Party and UserLogin are referentially circular). I think there is a cleaner
way to do this that would also allow for integrity checking of the denormalized
data.
I can't say I have any experience with gzipped xml. Would you simply
decompress it and read it like normal?
Direct migration from one delegator to another might be beneficial as well.
Because their is sync functionality, I would think this may be rather easy to
accomplish.
Anyway, just some more thoughts in this direction. This patch works well
double plus good :-)
vote +1
> entityImportDir does not retry failed files
> -------------------------------------------
>
> Key: OFBIZ-757
> URL: https://issues.apache.org/jira/browse/OFBIZ-757
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: framework
> Reporter: Andrew Sykes
> Priority: Minor
> Attachments: WebtoolsServices.java.patch
>
>
> It looks like the code for entityImportDir should retry failed files in case
> referential integrity problems are fixed by a subsequent file, but this
> doesn't happen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
