[
https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-1131 at 3/3/12 7:18 AM:
---------------------------------------------------------------
For oracle inserts if a table has an autoincrement column with a name in source of
columnname:SEQUENCE=sequencename.val, then we'll use the sequence value in the insert
submitted to Oracle if no value has been set for that column.
For any other sequence usage you'd have to model the sequence as a UDF or procedure
depending on how you need to call it and whether you need the value to be inlined or
obtained from a separate statement.
was (Author: shawkins):
For oracle inserts if a table has an autoincrement column with a name in source of
:SEQUENCE=sequencename.val, then we'll use the sequence value in the insert submitted
to Oracle if no value has been set for that column.
For any other sequence usage you'd have to model the sequence as a UDF or procedure
depending on how you need to call it and whether you need the value to be inlined or
obtained from a separate statement.
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: 8.1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira