I have a feature class in an Oracle 12c geodatabase.
The feature class has a type
column. The column has a coded domain.
I would like to limit user's ability to edit the features based on the type
of feature. I would ideally do this based on their privilege/role in the database.
Example:
- Where
type
=SIDEWALK
, only users in theROLE_EDITOR_GROUP_A
can edit - Where
type
=TRAIL
, only users in theROLE_EDITOR_GROUP_B
can edit - Where
type
=CYCLING
, only users in theROLE_EDITOR_GROUP_C
can edit
How can I achieve this level of control?
Note:
Due to the dependency that other enterprise systems have on the data, it is our preference to not split out the different types
of features into separate feature classes. We feel that single feature class would have these benefits:
- Simpler and more robust than unioning together separate feature classes to get all of the records into a single view
- Easier to enforce unique IDs
- Easier for editors to avoid duplicate or overlapping geometry
- Simpler in general to integrate with other critical enterprise systems
type
field doesn't even contain the text on which you want to key. Using a UNION ALL view for display from three feature classes would permit three different editing roles, but wouldn't address all your "Note" items,