[
https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1131.
-----------------------------------
Resolution: Done
Added two new jdbc importer properties:
importSequences, sequenceNamePattern. If a source does not support sequence import an
info log will be emitted. Initially supported sources are H2, Oracle, SQL Server 2012+,
PostgreSQL, DB2.
The docs were updated in the relevant sections to reference the new features. We can
consider from here whether to add a first class sequence - there is a new extension
metadata property to designate a function as a sequence, which does allow these functions
to be distinguished without relying just on a naming convention.
This logic is compatible with the Teiid hibernate dialect, but the documentation there
does suggest creating a virtual procedure/function as well.
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.5.0#75005)