Kevin Grittner kgri...@ymail.com wrote:
Michael Paquier michael.paqu...@gmail.com wrote:
I am not sure that adding a boolean flag introducing a concept
related to matview inside checkRuleResultList is the best
approach to solve that. checkRuleResultList is something related
only to rules,
Michael Paquier michael.paqu...@gmail.com wrote:
I am not sure that adding a boolean flag introducing a concept
related to matview inside checkRuleResultList is the best
approach to solve that. checkRuleResultList is something related
only to rules, and has nothing related to matviews in it
Ashutosh Bapat ashutosh.ba...@enterprisedb.com wrote:
CREATE MATERIALIZED VIEW statement ends up being CREATE TABLE AS
statement underneath with table type matview. In that case, why
don't I see special treatment only for materialized view and not
CTAS in general, which allows column names to
t.katsumata1...@gmail.com t.katsumata1...@gmail.com wrote:
I'm testing the Materialized View.
When I've tried to create materialized view with specified
column_name, I got an ERROR.
example:
- Creating original table
CREATE TABLE t ( i int );
- Creating materialized view with column_name
CREATE MATERIALIZED VIEW statement ends up being CREATE TABLE AS statement
underneath with table type matview. In that case, why don't I see special
treatment only for materialized view and not CTAS in general, which allows
column names to specified like the case in the bug reported.
On Fri, Nov
