[
https://issues.jboss.org/browse/TEIID-1822?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1822:
---------------------------------------
To elaborate more on a temporary table approach, I think this enhancement could be
expressed as adding limited support for global temporary tables and expanded create table
syntax.
If we added the ability to use create table AS clause, the IF NOT EXISTS clause (since it
would be non-durable), and index definition in the create statement, then a single CREATE
GLOBAL TEMPORARY TABLE IF NOT EXISTS tbl ... AS SELECT ... statement would be sufficient
to define a temporary table that fits your needs. We could also allow the matview cache
hint to apply to the statement so that you could control the memory preference and ttl.
For simplicity the table would be non-updatable, but the matview update procedure could
apply. Global temporary tables would be visible in user queries, but would not be visible
in views or procedures.
Dynamically Defined Materialized Views
--------------------------------------
Key: TEIID-1822
URL:
https://issues.jboss.org/browse/TEIID-1822
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like to be able to query a dynamically defined materialized view. For example,
suppose I issue the query
/* mat-view */ SELECT * FROM blah WHERE x='abc'
Optionally (probably based on a hint), I'd like the following query to execute
against the data set returned by the previous query rather than going back to the data
source:
/* use-mat-view */ SELECT * FROM (SELECT * FROM blah WHERE x='abc') GROUP BY
a
To make this truly useful, I'd like to define indexes. Something like:
/* mat-view(index-on:a,b,c) */ SELECT * FROM blah WHERE x='abc'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira