2011

If the view contains a join, columns that identify each row uniquely must
also be exposed.
If a class has no primary key, you can still expose it in AutoCAD Map 3D,
but it will be read only.
■ For Oracle data stores, if there is geometry in the view, there must be an
entry in user_sdo_geom_metadata for that geometry. This will provide the
spatial context and coordinate system information.
■ For Oracle non-simple views, you can specify which columns to use for a
primary key for the resulting feature class. Provide this information with
the view, as shown in this example:
alter view <viewname> add constraint <constraintname> primary key
(columnnames) disable novalidate;
NOTE This procedure is needed only for FDO (page 2062)-enabled schemas. For
existing schema data stores, AutoCAD Map 3D automatically displays the view as
a feature class, with no further action on your part.
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).
To create a feature class that maps to a database view
1 Create an FDO-enabled data store.
You can use the Schema Editor to do this. See
Creating a Schema (page
596)
2 Create a database view using the native tools for your database.
For Oracle, use sqlplus. For SQL Server, use sqlcmd. For MySQL, use
mysql.
3 Reconnect to the data store in AutoCAD Map 3D.
4 In the Schema Editor (page 1739), select the target schema Name and click
New Feature Class.
For information about creating feature classes and properties, see Editing
a Schema
(page 610).
5 If the Logical Feature Class tab is displayed, click the Physical
Configurations tab.
Exposing a Native Database View in a Schema | 605