[
https://issues.jboss.org/browse/TEIID-1092?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1092:
----------------------------------
After consulting the original case and various dbms usages of variables I believe this can
be satisfied with only session level (and likely non-transactional) variables. The
simplest approach is to not further the usage of set/show syntax nor leverage \@variables,
but to just introduce new built-in functions such as 'object teiid_session_set(string,
object)' and 'object teiid_session_get(string)'. By backing the values in the
Session object, they would be available via UDFs and at the translator level.
Request to have Global Variables
--------------------------------
Key: TEIID-1092
URL:
https://issues.jboss.org/browse/TEIID-1092
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 8.4
Customer is requesting a Global Variable. They want the variable to persist outside of
one procedure to other spawned procedures and subsequent queries.
--
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