Good spot Andrea, it was indeed the migration we did.
Alexandre
Le dim. 23 avr. 2023 à 20:13, Andrea Aime
a écrit :
> Or just not cleaning them at all... Pretty common use case: migrate lots
> of separate JDBC stores from stand alone to JNDI, to save on connections.
> Different store factory, e
Or just not cleaning them at all... Pretty common use case: migrate lots of
separate JDBC stores from stand alone to JNDI, to save on connections.
Different store factory, exactly the same feature types.
If one wants wipe out everything, it's simple: delete the store with
recurse first, then recre
The REST api is simple.
I would expect you are making that call as part of migrating a dataset from
oracle to postgis and will be cleaning up the feature types next.
On Sun, Apr 23, 2023 at 1:51 AM Alexandre Gacon
wrote:
> Hello,
>
> Currently, if you send a PUT request on a datastore with a to
Hello,
Currently, if you send a PUT request on a datastore with a totally
different definition of the datastore (for example, migrating from a
directory of shapefile to a pregen feature datastore), GeoServer accepts
the request and you got a 200 return code.
But the GS configuration is totally br
