Hi all, We have been moving a set of services from a proprietary WFS-product (SnowFlake) to Geoserver - both on Oracle. Luckily we had some app schemas to fulfil and have come pretty close to the previous output.
We have had a serious problem, though, with Joining JDBC Featuresource on tables where the primary key consists of several columns. The output SQL - at least of version 24.2 - in this case seems gibberish (invalid SQL with partial select criteria and even a "from" pasted into the "ON"-part of the joins). We have debugged quite a bit and have a patched version (specifically of one file in version 24.2), which we would like to contribute back to the project if possible. The few line changes can be seen here: https://github.com/Septima/geotools/commit/673cff35d72682b51b986943a0a4d8cb92552eb9 As our tests are based on a Geoserver on an Oracle DB, I have not found an easy way of writing a simple test case to prove the issue. But would of course like to write one up, if some guidance could be provided. The changes are so few (I suspect the original code never encountered composite primary keys) that someone might even "just" port it ref. the contribution guide. Anyways - I would like the list to advice, where to go from here? Thank you, Gregers *Hans Gregers Hedegaard Petersen* Partner, Seniorkonsulent greg...@septima.dk -------------------------- Septima P/S Frederiksberggade 19, 2. 1459 København K www.septima.dk Tlf: +45 7230 0672 Direkte: +45 9132 6945 Cvr: 34900841
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel