This should now be fixed in the nightly builds.
Ian
On Thu, 9 Jun 2022 at 17:53, emmexx wrote:
> On 6/9/22 6:00 PM, Ian Turton wrote:
> > I went ahead a made a report -
> > https://osgeo-org.atlassian.net/browse/GEOT-7161
>
> Thank you.
>
> And thank you for the Like workaround but I'm not sure
On 6/9/22 6:00 PM, Ian Turton wrote:
> I went ahead a made a report -
> https://osgeo-org.atlassian.net/browse/GEOT-7161
Thank you.
And thank you for the Like workaround but I'm not sure it can work in my
case.
maxx
___
Geoserver-users maili
I went ahead a made a report -
https://osgeo-org.atlassian.net/browse/GEOT-7161
Ian
On Thu, 9 Jun 2022 at 15:33, Ian Turton wrote:
> 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
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 th
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
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 w
I want to use WPS Aggregation process to get a pivot table based on some
attribute for a subset of the features of a layer.
[https://docs.geoserver.org/latest/en/user/services/wps/processes/gs.html#aggregation-process]
I started with a simple gs:CollectGeometries:
http://www.w3.org/2001/XMLSchema