That looks like a bug, the JDBCStore should not be passing strMatches to
Postgres without modifying it or (more likely) handling it in code after
the results are returned. Can you file a bug report at
https://osgeo-org.atlassian.net/jira/software/c/projects/GEOS including the
WPS you are sending that fails and that log file extract.

If you need a workaround in the mean time a Like filter should be able to
give you the same functionality,

Ian

On Thu, 9 Jun 2022 at 15:02, emmexx <emm...@tiscalinet.it> wrote:

> On 6/9/22 12:19 PM, Ian Turton wrote:
> > That looks like an SQL error message - can you turn on
> > GEOTOOLS-DEVELOPER logging and try again, then post the relevant part of
> > the log file - it should include the actual SQL being sent to the
> database.
> > And if you could mention the type of database and the version of
> > GeoServer you are using that will help too,
>
> I Attach the relevant log.
>
> Build Information
>
>     GeoServer Version
>     2.19.0
>     Git Revision
>     24c5d0b5a1b170f09e383ba35aae63f2ae9a2925
>     Build Date
>     18-Mar-2021 14:59
>     GeoTools Version
>     25.0 (rev d187663948b47212514991a71c0fc3021908b034)
>     GeoWebCache Version
>     1.19.0 (rev 1.19.x/c3b897ec57838c49f4cbb325c1e9a7678f9edd98)
>
> PostgreSQL 9.2.24
>
> postgis_version()
> 2.0 USE_GEOS=1 USE_PROJ=1 USE_STATS=1
>
> I tested the query that you can find in the log and, of course, it
> doesn't work because postgresql has not a strMatches function.
> In my notes about filters for my tables I found the equivalent of
> strMatches:
>
> Select * from myTable where myField ~ '.*\y(131)\y.*'
>
> But probably you already know that.
>
> Let me know if you need other info.
>
> Thank you
>   maxx
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 
Ian Turton
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to