Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.5.7
-
Component/s: arcsde plugin
-
Labels:None
-
Environment:ArcSDE 9.2/9.3, Oracle 10g, MS SQLServer 2000
Description
Currently the ArcSDE DataStore supports reading and writing versioned featureclasses only on the database DEFAULT version.
Make it so an optional datastore creation parameter can be passed in order for the resulting datastore instance to work upon a specified version, by version name.
Since ArcSDE versions are database wide, and featureclasses need to be registered as versioned in order to be seen among the different database versions, there´s an open question on how should it behave with respect to non versioned featureclasses:
I an ArcSDE DataStore is created to work against a given version other than the DEFAULT one, should it still display availability of non versioned featureclasses, or should it report only the versioned featureclasses?
I would opt for the later option...
Issue Links
| This issue is depended upon by: | ||||
| GEOS-3152 | ArcSDE DataStore level versioning support |
|
|
|
Also tested on GeoServer (tunk). Set up a versioned datastore and a non versioned one. Set up the same versioned FeatureType on both. Make edits to one, open both in OL preview, they differ as expected per the edits made.
Still unanswered if a versioned datastore should only contain the versioned feature types, or the non versioned too as the one working against the DEFAULT version does.
My inclination changed from the comment above. I would say it should show up both the versioned and non versioned feature types, since the "non versioned" datastore actually works against the DEFAULT version, so there's NO difference between one and the other, they just happen to work against different versions.