On Mon, Oct 2, 2023 at 12:10 PM Carsten Klein <c.kl...@datagis.com> wrote:

> Seems like the actual problem is, that my new function's class is not
> registered in the PostgreSQL Store's FilterCapabilities. However, I'm
> planing a private plugin-based (SPI) solution for this. How could I modify
> (extend) FilterToSqlHelper.createFilterCapabilities?
>
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?


> Couldn't there be a more extensible way to declare a SPI provided function
> "SQL encodable" for a certain Store (e.g. PostGIS)? Maybe a tag interface
> "SqlEncodable" could do that job?
>
No, it does not make sense... a filter may be sql encodable in one
database, but not in another, and a function is available
for the whole system. I doubt there are many functions that are sql
encodable in all databases we support.

It seems you need something that is specific to your own use case, and also
specific to one database: probably the most appropriate
path is for you to create and register a new data store factory, which ends
up subclassing PostGISDialect and return a different
FilterToSQL implementation (likely a subclass of the existing one).

Or maybe we could have some plugin (a new SPI) that can add entries to the
capabilities document, given a specific database.

Jody, any other ideas?

Cheers
Andrea

==

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to