Hi snuffy, The joining work is legacy of Niels Charlier during his time with our organisation, so I may not be 100% correct. >From my understanding, this is because the same rows from the linked table could be chained by multiple parents from the main table. Therefore the parent id is needed as foreign key to distinguish the parents.
e.g. super class id| joining condition ================================= 1 | x 2 | y 3 | x 4 | z sub class id | joining condition ======================= a | x b | y c | z Row 1 and 3 in the super class matches the same sub class rows (sub class id = a). Joining generates the following result set using INNER JOIN: sub class id | joining condition | super class id =================================== a | x | 1 a | x | 3 b | y | 2 c | z | 4 Joining relies heavily on sorting so it doesn't have to run so many queries. The super class id here is used to signal when to stop building the chained feature for the parent. I hope that makes sense. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/App-Schema-Inheritance-question-tp5081362p5083567.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
