...
Tags
spatialengine
Properties
Name | Type | Required | Description |
|---|---|---|---|
id | string | yes | Unique identifier |
dbtype | 'sqlserver' | yes | The name of the driver to use, in this case sqlserver |
host | string | yes | The hostname or ip address of the SQL Server |
host | |||
port | number | yes | The port number that the SQL Server instance is running on |
database | string | no | The database to be connected to |
instance | string | no | The |
SQL Server instance to be connected to | |||
integratedsecurity | boolean | no | Login as current windows user account. Works only in windows. Ignores user and password settings. |
url | string | no | JDBC URL connection string, full URL that completely replaces the URL constructed from the settings listed above (host, port, database, instance and integratedsecurity) |
schema | string | no | The schema used when connecting to the database |
user | string | yes | The userid used when connecting to the database |
passwd | string | yes | The password used when connecting to the database |
namespace | string | no | The namespace prefix |
minconnections | integer | no | The minimum number of pooled connection. Default 1 |
maxconnections | integer | no | The maximum number of open connections. Default 10 |
validateconnections | boolean | no | Check connection is alive before using it. Default false |
fetchsize | integer | no | The number of records read with each |
interaction with the |
DBMS. Default 1000 | |||
connectiontimeout | integer | no | The number of seconds the connection pool will wait before timing out attempting to get a new connection. Default 20 (seconds) |
primarykeymetadatatable | string | no | The optional table containing primary key structure and sequence associations. Can be expressed as 'schema.name' or just 'schema' (if the table name is 'GT_PK_METADATA'). Default none |
maxopenpreparedstatements | integer | no | Maximum number of prepared statements kept open and cached for each connection in the pool. Set to 0 to have unbounded caching, to -1 to disable caching. Default 50 |
geometrymetadatatable | string | no | The options table containing geometry column metadata information. |
usenativegeometryserialization | boolean | no | Use native SQL Server serialization, or WKB serialization. Default is false. |
forcespatialindexusageviahints | boolean | no | When enabled, spatial filters will be |
accompanied by a WITH INDEX sql hint forcing the usage of the spatial index. Default is false. |
Sub-tags
None
Content
None
Examples
...
| Code Block | ||
|---|---|---|
| ||
<spatial:spatialengine id="sqlserver">
<dbtype>sqlserver</dbtype>
<host>sqlhost</host>
<port>1434</port>
<database>INTERNAL</database>
<user>gis</user>
<passwd>hak0rz</passwd>
<schema>GIS</schema>
<minconnection>2</minconnections>
<validateconnections>true</validateconnections>
</spatial:spatialengine> |
SQL Server connection using a URL
| Code Block | ||
|---|---|---|
| ||
<spatial:spatialengine id="sqlserver"> <dbtype>sqlserver</dbtype> <url>jdbc:sqlserver://sqlhost:1434;DatabaseName=INTERNAL</url> <user>gis</user> <passwd>hak0rz</passwd> <schema>GIS</schema> <minconnection>2</minconnections> <validateconnections>true</validateconnections> </spatial:spatialengine> |
Row Identifiers
Weave needs to be able to uniquely identify each row in a particular table, normally it would do this using the primary key of the table, but sometimes a primary key has not been specified so this information must be provided another way.
...
If the primary key for a table can not be determined by Weave directly from the database then the information can be provided by creating a table or directly embedding the information in the spatial engine configuration.
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'). Where: |
pk_sequence | The name of the database sequence to be used when generating a new value for the pk_column. The pk_sequence value only need to be set if the pk_policy is 'sequence'. |
Using primary key metadata configuration
You can also specify the above information directly in the spatial engine 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="sqlserver">
<dbtype>sqlserver</dbtype>
<host>sqlhost</host>
<port>1434</port>
<user>gis</user>
<passwd>hak0rz</passwd>
<schema>GIS</schema>
<minconnection>2</minconnections>
<validateconnections>true</validateconnections>
<primarykeymetadata>
<table schema="dbo" name="park" column="gid" policy="autogenerated"/>
<table schema="dbo" name="property" column="park_id" type="autogenerated"/>
<table schema="dbo" name="road" column="objectid" type="autogenerated"/>
</primarykeymetadata>
</spatial:spatialengine> |
...
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.
Name | Description |
|---|---|
name | The table name |
schema | The optional table schema |
type | The geometry type (point, linestring, polygon, multipoint, multilinestring, multipolygon) |
srid | The geometry srid |
dimension | The geometry dimension |
Using geometry metadata configuration
...