[
https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3301.
-----------------------------------
Resolution: Done
Added the view based upon sys.columns and the metadata properties
http://www.teiid.org/translator/spatial/2015}coord_dimension
http://www.teiid.org/translator/spatial/2015}srid
http://www.teiid.org/translator/spatial/2015}type
Both this and the spatial ref sys will be added to docs as well.
The appropriate metadata will be populated on a dynamic import as well for oracle and
postgresql - but I couldn't find where mysql exposes the same information. We'll
by default assume 2 coordinate dimensions, a zero SRID, and a GEOMETRY type.
The last remaining metadata piece to tackle would be associating the srid on reads from
the sources. For mysql we could use their internal format, for pg we could use ewkb, and
oracle could use ewkt. Or we could just assume the metadata will be set and associate the
column property with the result - however that will not work for anything other than a
simple select.
Add GEOMETRY_COLUMNS view
-------------------------
Key: TEIID-3301
URL:
https://issues.jboss.org/browse/TEIID-3301
Project: Teiid
Issue Type: Feature Request
Reporter: Tom Arnold
Assignee: Steven Hawkins
Labels: spatial
Fix For: 8.10
Another OGC Simple Features implementation detail. Basically this is like a specialized
version of SYS.COLUMNS, and would be used to support GIS software (like GeoServer).
http://www.carocoops.org/resources/doc/postgis/x321.html
{code}
CREATE TABLE GEOMETRY_COLUMNS (
F_TABLE_CATALOG VARCHAR(256) NOT NULL,
F_TABLE_SCHEMA VARCHAR(256) NOT NULL,
F_TABLE_NAME VARCHAR(256) NOT NULL,
F_GEOMETRY_COLUMN VARCHAR(256) NOT NULL,
COORD_DIMENSION INTEGER NOT NULL,
SRID INTEGER NOT NULL,
TYPE VARCHAR(30) NOT NULL
)
{code}
I think we could implement this by storing SRID & friends as column properties, and
then creating a view on SYS.COLUMNS & SYS.PROPERTIES.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)