[
https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3301:
---------------------------------------
What is the concern here?
I'm saying that as long as the source query has the direct projection of a geometry
value, then we'll easily be able to associate the srid - but for a query with
functions creating geometry values or inline views (although the logic to trace the value
would be easy in the engine) would be more difficult to associate the srid.
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)