[
https://issues.jboss.org/browse/TEIID-2577?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2577:
---------------------------------------
I still do not see the validity of this JIRA's issue in
comparison to the Derby/H2 procedures, as I do not look at translation layer as execution
of procedure construct, but as any arbitrary statement. Re-cursing back into Teiid engine
for processing, seems bad not only in terms of processing, but also should expose same
transactional issues as that of client layer. If this is right, I feel that it will
(ab)used more for wrong reasons.
I don't quite follow this. Imagine for a second that we did not have a virtual
procedure language. How would someone go about writing a stored procedure? They would
need access to some connection to execute a series of statements and other logic.
The issue you may have with this is that it's being introduced at the translator layer
rather than a specific api for "java stored procedures" - which is somewhat
related to
https://issues.jboss.org/browse/TEIID-147 although that could also be
envisioned as still being user/designer driven with scriptable java.
Translator API to provide session backed connection
---------------------------------------------------
Key: TEIID-2577
URL:
https://issues.jboss.org/browse/TEIID-2577
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Provide an API (probably from an ExecutionContext) to obtain a JDBC connection to the
same Teiid instance under the client's session.
--
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