This behavior change is in the 2022_07 bundle. In the 6.32 release, the bundle is disabled by default.
For the most up-to-date details about the version and date in which it will be enabled, as well as other release-related details, see the Behavior Change Log.
One limitation of materialized views is that the Time Travel feature is not supported. However, when you run the CREATE MATERIALIZED VIEW command, it was possible to specify a Time Travel clause (e.g. AT) for the base table of the view.
Specifying a Time Travel clause in CREATE MATERIALIZED VIEW now results in an error:
|
Previously:
|
Specifying a Time Travel clause (e.g. AT) in CREATE MATERIALIZED VIEW did not produce an error.
For example, the following statements executed successfully without any errors:
- Example 1:
create or replace materialized view mv as
select * from basetbl at(offset => -2);
- Example 2:
create or replace materialized view mv as
select * from basetbl at(timestamp => $ts);
- Example 3:
create or replace materialized view mv as
select * from basetbl at(statement => $uuid_dml);
|
|
Currently:
|
Specifying a Time Travel clause (e.g. AT) in CREATE MATERIALIZED VIEW now produces the following error:
002274 (42601): SQL compilation error: Invalid materialized view:
Time travel on base table in line X at position Y.
|
Ref: 790
