[
https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1131:
----------------------------------
Fix Version/s: (was: 8.2)
Pulling out of a release bucket, since this can now be workaround in several other ways.
If it's acceptable to retrieve the value using a separate call then the native
procedure and native-query metadata can both be used to get at sequence values.
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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira