2011

Table Of Contents

Each provider maps a correspondence between a schema element and a

physical object in a feature source. The physical structure of feature sources

varies by provider, as do the types of schema mappings and default

settings. Oracle, for example, maps each feature class onto a table in the

Oracle database where the feature source resides, giving the class and

table the same name. You can override these defaults by changing the

settings on the Physical Configurations tab. The settings on this tab vary

by provider. The tab is unavailable for providers whose defaults cannot

be changed.

8 Click Apply.

9 Repeat the preceding four steps as required to edit other schema elements.

10 Click OK to make all the changes permanent.

Deleting Schemas

When you delete a

schema (page 2073), feature class (page 2063), or property (page

2071) in the Schema Editor, its icon disappears from the Schema tree, along with

the icons of its child elements (if any). However, the changes are not transferred

to the underlying

feature source (page 2063) until you apply them. If you delete

a feature class, for example, the class and its properties are removed from the

Schema tree, but its table remains in the feature source until you click Apply.

You can

undo (page 614) changes until you click Apply.

NOTE You cannot delete a schema, feature class, or property if feature data exist

for that item.

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).