...
Column | Description |
|---|---|
table_schema | Name of the database schema in which the table is located. |
table_name | Name of the table to be published |
pk_column | Name of a column used to form the feature IDs |
pk_column_idx | Index of the column in a multi-column key. In case multi column keys are needed multiple records with the same table schema and table name will be used. |
pk_policy | The new value generation policy, used in case a new feature needs to be added in the table ('assigned', 'sequence' or 'autogenerated'). |
pk_sequence | The name of the database sequence to be used when generating a new value for the pk_column. |
Using primary key metadata configuration
You can also specify the above information directly in the spatial engin configuration.
Name | Description |
|---|---|
| name | The table name |
| schema | The optional table schema |
| column | The column in the the table that contains the unique id |
| policy | How the key is generated |
| sequence | The name of the database sequence to use if the policy is 'sequence' |
| Code Block |
|---|
<spatial:spatialengine id="sdbeos">
<dbtype>oracle</dbtype>
<host>sdbeos</host>
<port>1521</port>
<database>staging</database>
<user>data_viewer</user>
<passwd>ENCSSJKXUMJBMTPGEJFGCXCQFXJJZUTMJZJ</passwd>
<schema>ASSETS</schema>
<primarykeymetadata>
<table schema="ASSETS" name="PARK" column="GID" policy="autogenerated"/>
<table schema="ASSETS" name="PROPERTY" column="PARK_ID" type="autogenerated"/>
<table schema="ASSETS" name="ROAD" column="OBJECTID" type="autogenerated"/>
</primarykeymetadata>
</spatial:spatialengine> |
Geometry metadata table
The Oracle data store will, by default, look into the MDSYS.USER_SDO* and MDSYS.ALL_SDO* views to determine the geometry type and native SRID of each geometry column. Those views are automatically populated with information about the geometry columns stored in tables that the current user owns (for the MDSYS.USER_SDO* views) or can otherwise access (for the MDSYS.ALL_SDO* views).
...
When the table is present the store will first search it for information about each geometry column to be classified, and fall back on the MDSYS views only if such table does not contain any information.
Using geometry metadata configuration
...
configuration
As of Weave 2.5.16 it's possible to specify the information contained in the geometry metadata table directly in the spatial engine configuration.
...