Andrea,
There is nothing planned to support this functionality. We are more
interested in nudging people to contribute
open code to benefit everyone.
Unless you're going to write functions that are very specific to your
case, and would not be of interest to the larger community?
Maybe I didn't explain that correctly. Basically, I'm keen to contribute
open code so that everyone could benefit from it. However, in this case,
I only need use two project-specific PostgreSQL functions in WFS
queries. Likely I'm the only person who needs these. Saying:
"However, I'm planing a private plugin-based (SPI) solution for this."
just means, that I'd like to add a private (my own) GeoTools plugin jar
to GeoServer's lib dir, that contains these two extra functions.
GeoTools' SPI approach makes this quite easy. However, it turns out,
that these functions get not SQL encoded, since these functions' classes
are not contained in the functions Set of the Store's
FilterCapabilities. (Actually, the query is split into a pre- and and
post-filter in the JDBCDataStore.)
Indeed, it would be cool if one can mark a function being "SQL
encodable" with the same easiness than publishing this function. That
would be something, others could benefit from as well...
[...]
Or maybe we could have some plugin (a new SPI) that can add entries to
the capabilities document, given a specific database.
You mean the FilterCapabilies of a specific store? That would be quite
helpful.
Cheers
Carsten
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
