Hello all,
I have posted the following question on GIS StackExchange, then remembered the
GeoServer lists, so I thought I would see if any one has any input.
https://gis.stackexchange.com/questions/306456/how-should-arrays-be-stored-in-postgresql-when-used-as-a-datastore-with-geoserve
The crux
On 17-12-18 16:06, Cliff Patterson wrote:
Hi Sorin,
All very good suggestions! Big thanks! I do like your final idea about
"materialized views". I was thinking the same thing since a simple
crontab job (at least in my Linux/PG world) would do it nicely.
No materialized views in ms sql server
Hi,
the issue has been fixed already, the fix seems to have been included in
2.14.1:
https://osgeo-org.atlassian.net/browse/GEOT-6178
Cheers
Andrea
On Tue, Dec 18, 2018 at 3:26 PM johnnyotoole wrote:
> Hi,
>
> I came across this problem now too with GeoServer 2.14.0 against an Oracle
> 12.1.0.2
When I configure the New SQLView, it is ok to use constant in Sql Clause, The
following code:SELECT seq, id1 AS node, id2 AS edge, cost,geom FROM
pgr_dijkstra('
SELECT gid AS id,
source::integer,
target::integer,
length::double pre
Hi,
I came across this problem now too with GeoServer 2.14.0 against an Oracle
12.1.0.2 database with geoserver-2.14.0-oracle-plugin and ojdbc8.jar.
The problem seems to be that the generated SQL is missing a space between
the table name and the "WHERE". If I run the SQL as per the log file I ge
