added information about geometry_field from xml_configuration [markdown]
parent
0262612d55
commit
01aaaf683e
1 changed files with 1 additions and 1 deletions
|
@ -45,7 +45,7 @@ To check if the PostGIS plugin built and was installed correctly, try the usual
|
||||||
| user | string | username to use for connecting | |
|
| user | string | username to use for connecting | |
|
||||||
| password | string | user password to use for connecting | |
|
| password | string | user password to use for connecting | |
|
||||||
| table | string | name of the table to fetch, this can be a sub-query | |
|
| table | string | name of the table to fetch, this can be a sub-query | |
|
||||||
| geometry_field | string | name of the geometry field, in case you have more than one in a single table | |
|
| geometry_field | string | name of the geometry field, in case you have more than one in a single table. This field and the SRID will be deduced from the query in most cases, but may need to be manually specified in some cases.| |
|
||||||
| geometry_table | string | name of the geometry table ??? | |
|
| geometry_table | string | name of the geometry table ??? | |
|
||||||
| srid | integer | srid of the table, if this is > 0 then fetching data will avoid an extra database query for knowing the srid of the table | 0 |
|
| srid | integer | srid of the table, if this is > 0 then fetching data will avoid an extra database query for knowing the srid of the table | 0 |
|
||||||
| extent | string | maxextent of the geometries | determined by querying the oracle metadata for the table |
|
| extent | string | maxextent of the geometries | determined by querying the oracle metadata for the table |
|
||||||
|
|
Loading…
Reference in a new issue