The update parameter compares usages or features in the published database against usages and features in the source database, then makes changes to the published database.
The following example shows the update parameter with addFeature option.
caris_hpd_web_publisher -addFeature -sourceDBService=HPDdb -sourceUser=hpd26user -sourcePass=hpd26pass -destDBService=WEBdb -destUser=hpdwebuser -destPass=hpdwebpass -usage_name="Harbour(2500-4999)" -feature_acronym=LNDARE -update -symbolize |
In the above example, the update parameter compares the land area (LNDARE) features on the Harbour usage in WEBdb against the LNDARE features on the Harbour usage in HPDdb. The following changes are made in WEBdb:
• New LNDARE features are added.
• Deleted LNDARE features are removed
• Modified LNDARE features are changed.
Note that the symbolize parameter is also used. This parameter must be included if you want to apply symbolization with the update feature. If the symbolize parameter is not included the new LNDARE features are not symbolized.
In this example, the parameters follow a structured syntax.
caris_hpd_web_publisher addFeature HPDdb hpd26user hpd26pass WEBdb hpdwebuser hpdwebpass "Harbour(2500-4999)" LNDARE "hpdobjects" true true |
Notice that the value true is included twice. The first true value represents the symbolize parameter and the second true represents the update parameter. The symbolize parameter must precede the update parameter. If symbolization is not included then the symbolize parameter must be set to false.
Also, the option that uses a structured syntax must include the catalog_name parameter if the update option is used.