Thanks for the answer! It is intended, then.
As REST can create a table, I thought there could be a way to do other
operations on it, other than inserts, updates, deletes, etc, on records. I
guess I wouldn't have searched for it if REST couldn't create tables.

Now it is only by curiosity: with a PUT command for, lets say, add an
attribute to a layer, it will change metadata. Doing so, it will make
metadata incoherent with database and will raise errors and prevent me to
read that layer. Is this behaviour intended?

Sent from:

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
- Earning your support instead of buying it, but Ian Turton:
- The GeoServer user list posting guidelines:

If you want to request a feature or an improvement, also see this:

Reply via email to