Gabriel, I agree that we should be using a proper ORM solution, but I do not think that the O-R mapping process can be separated from the target application schema. I do not see why you think these are orthogonal. It makes most sense to me to have a GUI that allows the user to navigate their database schema and the target application schema at the same time and make the connections between them. Significant problems arise when the information models of the database and XML schema are incompatible, such as different association cardinality.
The feedback I get from our most experienced deployer is that the most time-consuming part of using app-schema is constructing the database views required to adapt a maintenance database schema into the information model of the target XML application schema. In my view (no pun intended), the biggest win would be a complete solution that would allow a reversible (to support filter queries) mapping between the target application schema and the database schema, without the use of any intermediate views. This would be driven by a GUI with access to the target application schema and the database schema. A one-step solution would also permit query optimisation, which at the moment is prevented not only by the intermediate simple features but also by the database views. Kind regards, Ben. On 29/09/10 22:18, Gabriel Roldán wrote: > I think the app-schema module (since a long long time ago) should be > split into two, because it's taking care of two orthogonal concerns: > - app schema mapping > - O/R mapping > One thing that would be very worth to try,imho, is to have a Hibernate > Spatial datastore so we don't have to reinvent the wheel wrt OR mapping, > and then thea app schema mapping can use one of those for the final > tweaks to make it app-schema conformant. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
