Shaw, you can use app-schema either way. Denormalised views may be more suitable for multivalued simple properties. Feature chaining may be better if the properties have structure or are features, and may make later modification easier as the mapping is encapsulated.
Kind regards, Ben. On 08/03/11 08:39, Shaw Innes wrote: > Thanks Ben > Those samples helped me get it working for "simple" complex features - but > I'm stuck with the chaining side of things. > > In my original example I said I have two tables in the database - and I > was imagining that I would have two features in the output, however I just > read a previous post you made to someone regarding feature chaining and > suggested they create a view in the database to return the parent feature and > all child records in a 1:many join view. Is this the correct way to perform > feature chaining? Ie. does that mapping occur in the geoserver app schema > module, rather than having it perform two independent object queries and join > them? -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
