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".
SIS-519 Never-ending loop in AbstractFeature.equals/hashCode