[
https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-3369:
--------------------------------------
We can consider later if it makes sense to offer this on a per vdb
basis
The current approach works fine for my current use case but the value of providing a per
vdb parser is pretty high, IMO: As mentioned in
https://developer.jboss.org/message/928788#928788 I'm using the API to layer semantics
onto a query because the client cannot generate appropriate SQL. I can easily imagine a
case where some clients would generate proper SQL while others wouldn't and
discriminating based them by VDB makes a lot of sense.
Add a extension point to manipulate incoming sql
------------------------------------------------
Key: TEIID-3369
URL:
https://issues.jboss.org/browse/TEIID-3369
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
We should look at adding a client or server extension point for manipulating sql - just
the sql string, pre resolving. This will allow more flexibility in dealing with clients
that don't send queries directly understood by Teiid. For example a select for
update.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)