[
https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin...
]
Tom Arnold commented on TEIID-3301:
-----------------------------------
{quote}
but I couldn't find where mysql exposes the same information
{quote}
It doesn't (
http://dev.mysql.com/worklog/task/?id=2378). It looks like the GeoTools
MySQL module creates and manages a GEOMETRY_COLUMNS table. For now, we could place the
onus on the users to do the same; i.e., try to import from table if it exists.
{quote}
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.
{quote}
What is the concern here? The structure of the table implies that the values in a column
will all have the same SRID/type/etc. I think it's possible to mix these in practice,
but it's not a good idea. Will see if I can find something to back this up...
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)