 |
This document is archived and information here might be outdated. Recommended version. |
esriReplicaModelType Constants (ArcObjects .NET 10.4 SDK)
|
This document is archived and information here might be outdated. Recommended version. |
| ArcObjects namespaces > Geodatabase > ESRI.ArcGIS.GeoDatabase > Constants > E > esriReplicaModelType Constants (ArcObjects .NET 10.4 SDK) |
Indicates how the data will be stored in the child geodatabase.
| Constant | Value | Description |
|---|---|---|
| esriModelTypeSimple | 1 | Data is stored as simple features. |
| esriModelTypeFullGeodatabase | 2 | All data is stored the same way as in the parent geodatabase. |
The esriReplicaModelType enumeration contains values that represent different replica model types. This can be set for check-out, one way, and two way replicas.
The replica model type is set using the IGPReplicaDescription::ReplicaModelType property on a replica description. The model type may be set before or after initializing the replica description with the IGPReplicaDescription::Init method. See the GPReplicaDescription coclass for more information.
The members of this enumeration are:
esriModelTypeSimple=1 - Only simple data types are stored in the child. If the parent has annotation or dimension feature classes, the annotation or dimension feature classes are not stored in the child. If the parent has a topology or geometric network, the participating feature classes are stored in the child without the topology or geometric network. Storing only simple data types in the child allows edits to be made by a non-geodatabase editor. This is useful in systems where some of the data sources involved are not geodatabases. For example, you may want to apply edits made in a shapefile or a non-ArcGIS data format to your geodatabase. When synchronizing edits from simple features in the child to the parent, reactive behavior is applied in the parent to update topology dirty areas, maintain network connectivity and maintain annotation and dimension features.
esriModelTypeFull=2 - All features, including complex features, are stored in the child the same way they are stored in the parent. If the parent has annotation or dimension feature classes, the annotation or dimension feature classes will be stored in the child. If the parent has a topology or geometric network, it will be stored in a corresponding topology or geometric network in the child. Storing complex features in the child is useful in systems where all data sources involved are geodatabases, and you'll be using full geodatabase editors like the one provided in ArcMap. With this model, no additional geodatabase behaviour is applied when synchronizing because it has already been applied with the geodatabase editor in the child.