Hi,
If the datastore is JDBC, I think the purge makes sense to remove the
underlying tables. I know we thought of a process for user defined layers,
where users get to upload shapefiles that are ingested into the database as
tables to specific schemas (PostgreSQL/PostGIS tables). When the layer is no
longer required, removing them requires the GeoServer layer entries to be
deleted, then a DB admin is required to manually drop the tables in the
database. Having the PURGE on the REST call would make things, in our case,
easier.
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, A Polaris Alpha Company
[Description: Description: Description: cid:[email protected]]
From: Torben Barsballe [mailto:[email protected]]
Sent: Monday, September 18, 2017 4:01 PM
To: geoserver-devel <[email protected]>
Subject: Re: [Geoserver-devel] Rest Swagger Doc QA - Unimplemented parameters
Found another parameter that is declared in the code, but never actually used:
The "purge" parameter for datastore delete.
David - looks like you converted this endpoint, any comment?
As far as I can tell, this was blindly copied from the coveragestore delete
code, as I can find no purge parameter for datastore delete in the old rest api.
For coveragestore, purge is used to delete the underlying files in addition to
the store; is this something that could be useful for datastore? I feel like
databases might make this a bit more complicated.
Torben
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
