[
https://jira.jboss.org/jira/browse/TEIID-908?page=com.atlassian.jira.plug...
]
John Doyle commented on TEIID-908:
----------------------------------
DTP doesn't define what JDBC API to call, AFAIK plan's not a JDBC concept, right?
DTP provides an interface to implement to get the plan as a string and one to convert the
string to nodes. How we want to fetch the plan is not dictated by DTP. In the one DTP
implementation that does produce a plan (ingres), they read the plan from the log
who's location is provided by a system property.
FWIW I'm purposely not trying to define the call to our driver that we should have.
Nothing in the JDBC API jumps out at me as the right place to put this. ClientInfo
seems like the kind of generic bucket where it could go, but I don't think it belongs
there. I'm guessing that's why MMStatement has it's own set statement.
As far as the schema, I have just figured this would be hard coded.
Enable access to the query plan without reference to Teiid classes.
-------------------------------------------------------------------
Key: TEIID-908
URL:
https://jira.jboss.org/jira/browse/TEIID-908
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 6.2.0
Environment: Eclipse Data Tools Platform connection to Teiid.
Reporter: John Doyle
Assignee: Steven Hawkins
Eclipse Data Tools provides a framework for getting/displaying a query plan and I want to
implement it as part of our DTP plug-ins. Currently you can only get the query plan from
the MMStatement class, but DTP works only with the JDBC interfaces. Access to the query
plan via the JDBC APIs and core java classes will enable us to plug into the framework.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira