2011

Table Of Contents
NOTE This functionality affects geospatial feature data only. For information about
linking records in an external database to objects in a drawing, see
Overview of
Linking Database Records to Objects
(page 522). For information about moving
data between DWG and geospatial data stores, see
Migrating DWG Data to GIS
(page 628).
When you
edit the properties (page 711) in the Data Table, you can enter only
the values allowed by the constraint. For example, for a Roads feature, you
can specify that the values for the Number_Of_Lanes property be within the
range 1 through 8. If you enter 9 lanes, you will receive an error message.
You will see an error message as soon as you enter the invalid value. When
you check the feature in, your edits are validated again against the data store
and you may be notified of further errors, depending on the capabilities of
the data provider.
You cannot edit a schema to convert an existing field to use a different
constraint type if the table already contains data. The table must be empty.
Not every data provider supports all constraints. The following table shows
supported constraints by provider.
UniqueNot NullListRangeProvider
YesYesYesYesOracle
YesYesYesYesPostgr-
eSQL/PostGIS
YesYesYesYesSQL Server
YesYesYesYesSQL Server
Spatial
YesYesYesYesSQLite
YesYesNoNoMySQL
NoYesYesYesSDF
YesYesNoNoArcSDE
NoYesNoNoSHP
600 | Chapter 4 Managing Data