GeoServer

Layer level transaction configuration

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2.0-rc2, 1.2.0
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Right now the transaction level can only be set globally. It's an all or nothing affair. GeoServer should allow different layers to have different transaction settings. We also should allow more configuration options, like updates but not deletes and inserts. This is done in the backend, but there's no user interface for it currently.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

I actually got a user request complaining about a similar issue lately. They wanted to make GetFeature impossible on a certain layer, but not on others, and allow GetMap.
Which is not possible to get now even using the security subsystem, because if you disallow reading, you kill GetMap, and if you disallow GetFeature, you disallow it for every layer.

Show
Andrea Aime added a comment - I actually got a user request complaining about a similar issue lately. They wanted to make GetFeature impossible on a certain layer, but not on others, and allow GetMap. Which is not possible to get now even using the security subsystem, because if you disallow reading, you kill GetMap, and if you disallow GetFeature, you disallow it for every layer.
Hide
Permalink
Andrea Aime added a comment -

This can be obtained by using the security subsystem

Show
Andrea Aime added a comment - This can be obtained by using the security subsystem

People

  • Assignee:
    Chris Holmes
    Reporter:
    Chris Holmes
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: