Hi all, For the record, I'm utterly against deleting database tables through the geoserver REST API * It's absolutely dangerous * The REST API shall with GeoServer "resources", not infrastructure ones
If I wanted to delete a table through *a* REST API, I'd better run two queries, one to delete the geoserver FeatureType/Layer, and another one to delete the database table, for which there are existing solutions, for example PostgREST https://postgrest.org (not sure if that one lets you drop tables) but you get the idea. Cheers, Gabe On Mon, 12 Feb 2024 at 16:25, Jody Garnett <jody.garn...@gmail.com> wrote: > I am open to improvements and addition to the importer API (which offers > some control as it is responsible for the automatic creation of tables; it > has an opportunity to delete an existing table when replacing contents). > > See example > https://docs.geoserver.org/latest/en/user/extensions/importer/rest_examples.html#replacing-postgis-table-using-the-contents-of-a-csv-file > > > -- > Jody Garnett > > > On Feb 12, 2024 at 1:30:11 AM, Cécile Vuilleumier < > cecile.vuilleum...@camptocamp.com> wrote: > >> Hi all >> When creating a feature type in a database datastore with the REST API, >> GeoServer will create the corresponding table if it does not exist. >> We were wondering if similarly the deletion of a table was also possible >> when deleting the associated feature type and I found this discussion: >> https://sourceforge.net/p/geoserver/mailman/message/36221224/ >> Does anybody know if a proposal had been submitted? I couldn't find it on >> the GitHub wiki but I might have missed it. >> Many thanks, Cécile >> >> -- >> *camptocamp* >> >> *Cécile Vuilleumier * >> Geospatial developer >> www.camptocamp.com >> _______________________________________________ >> 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 >> > _______________________________________________ > 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 > -- Gabriel Roldán
_______________________________________________ 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
