[
https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1131:
---------------------------------------
With TEIID-2571 and TEIID-2572 it is straight-forward to represent sequences as source
functions. For sequences an Oracle example would be:
{code}
create foreign function seq_nextval () returns integer OPTIONS
("teiid_rel:native-query" 'seq.nextval')
{code}
could be called through Teiid as:
{code}
SELECT seq_nextval()
{code}
and would result in the source sql:
{code}
SELECT seq.nextval FROM DUAL
{code}
The same approach will work for postgresql, db2, etc. We still will want to consider if a
proper metadata/calling mechanism should be added and what to offer on import (for
pg/oracle at least sequences can be obtained through just DatabaseMetaData).
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