[
https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1131:
---------------------------------------
The import above will only work for pg/oracle. The other sources need specific metadata
queries to retrieve the sequences. So for full support we'd need to add additional
import logic with name patterns etc. to pull the names/datatype of the sequences. We
could expand our hibernate integration to get at that information - except it doesn't
provide the type, so we'd have to assume long.
Document/expand sequence support
--------------------------------
Key: TEIID-1131
URL:
https://issues.jboss.org/browse/TEIID-1131
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector, Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
Currently sequence workaround logic only exists for oracle and is undocumented. We
should look at expanding sequence support - even for dynamic vdbs, see SQuriel's
handling of system queries for retrieving sequence metadata.
At least allowing the workaround logic to work for all sources that support sequences
(Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)