[
https://issues.apache.org/jira/browse/OFBIZ-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Howe updated OFBIZ-810:
-----------------------------
Attachment: ArrangeSelfRelation.patch
ArrangeSelfRelation.patch
This will write records of entities that have a relationship with them self in an order that will allow for direct import.
This patch only takes into account the Parent<Entity>/ Child<Entity> relation name but allows the others to pass as well and points out where it can be improved to take into account more naming methods.
> Improve export/import services
> ------------------------------
>
> Key: OFBIZ-810
> URL:
https://issues.apache.org/jira/browse/OFBIZ-810> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: framework
> Reporter: Chris Howe
> Priority: Minor
> Attachments: ArrangeSelfRelation.patch
>
>
> In postgres (and likely other databases), relational integrity is handled by the database and therefore dummy keys that don't get written to the database will fail with referential integrity issues if records aren't entered in a specific order. To solve this dilemma, Andrew handled the import issue when the referential record in question would eventually exist by marking failed files for retry OFBIZ-757. Two additional scenarios would make it difficult to do straight export/import and thus serve as a true backup service.
> 1) foreign keys may not match the referenced record's case correctly (admin != ADMIN != AdMiN )
> 2) the necessary referenced record may be read later in an xml file and therefore will always fail referential integrity regardless of how many times it is retried
> 1 can be solved by allowing a check/correct service
> 2 can be at least partially solved by writing the xml file in an order where the referenced record gets written before the fk
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
