You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/06/27 14:23:00 UTC
[jira] [Commented] (SYNCOPE-1128) Content exporter does not sort
for internal foreign keys
[ https://issues.apache.org/jira/browse/SYNCOPE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064920#comment-16064920 ]
ASF subversion and git services commented on SYNCOPE-1128:
----------------------------------------------------------
Commit a6147996d2d14f1ce8f1b3f98e4e57788e464d90 in syncope's branch refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=a614799 ]
[SYNCOPE-1128] Now ordering table rows before export, also for 'internal' foreign keys
> Content exporter does not sort for internal foreign keys
> --------------------------------------------------------
>
> Key: SYNCOPE-1128
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1128
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1.8, 1.2.10, 2.0.3
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 1.2.11, 2.0.4, 2.1.0
>
>
> Some database tables created for JPA entities (say {{Realm}}) contain foreign key constraints related to other column(s) in the same table.
> This means that, when exporting the content as XML, the order in which their rows is report must take this conditions into account.
> This is currently not happening, as child Realms might be exported before parent Realms, thus generating errors during subsequent import.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)