[
https://issues.apache.org/jira/browse/SIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-520.
-------------------------------------
Resolution: Fixed
Fixed in commit {{911a413919d06cd4a549a4365c461e02adb622d3}}.
> SQLStore should avoid creating features with cyclic associations
> ----------------------------------------------------------------
>
> Key: SIS-520
> URL: https://issues.apache.org/jira/browse/SIS-520
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Storage
> Affects Versions: 1.0, 1.1
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
> Fix For: 1.2
>
>
> When {{SLStore}} analyses a database schema for table _A_, if anoter table
> _B_ has a foreigner key to table _A_, then {{SQLStore}} consider table _B_ as
> a "children" of _A_. It creates a property in feature _A_ containing a
> collection of associations to feature _B_ instances. However in Apache SIS
> 1.1, the feature _B_ instances keep a reference to their parent (the feature
> _A_). The result is a cyclic graph, which can cause problems as SIS-519.
> While SIS can generally handle recursivity, client code may not. So it is
> probably better to modify {{SQLStore}} for not providing an association from
> "children features" to their "parent feature".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
