2011

Table Of Contents
FDO Provider Capabilities
You use FDO (page 2062) to connect directly to a data source and work in its
native format. Each data source type uses its own
FDO provider (page 2063), and
each provider has different capabilities.
For example, Oracle and ArcSDE support locking on the feature level. When
you check out a feature, other users cannot edit it, even though they can view
your edits and edit other features in the feature source. Oracle and ArcSDE
also support persistent locking, so the object stays locked until you check it
back in.
SHP feature sources, on the other hand, support locking on the file level.
When you check out a feature, its entire SHP file is locked. Other users cannot
edit features from that file until you close the map, which releases your lock
(even if you still have features checked out at the time). Be careful to check
in your changes before you close the map.
Versioning (page 2078) allows multiple copies of a spatial dataset to be stored
and tracked by date of creation, date of change, and so on. Not every FDO
provider supports versioning.
The following table lists the level of locking, versioning, and schema editing
supported by each feature source type.
Edit
Schema
Persistent
Locking
VersionsLock LevelFeature Source
Type
YesNoNoNone
ArcSDE (page
316)
YesNoNoNoneMySQL (page
332)
NoNoNoFileODBC (page 342)
YesYesYesFeatureOracle (page 312)
YesYesYesFeaturePostgreSQL/Post-
GIS (page 340)
YesNoNoNoneSDF (page 337)
YesNoNoFileSHP (page 335)
Overview of Bringing In GIS Features | 307