Hello Guys,
ERROR: could not convert table b to a view because it has triggers
HINT: In particular, the table cannot be involved in any foreign key
relationships.
** Error **
ERROR: could not convert table b to a view because it has triggers
SQL state: 55000
Hint: In
salah jubeh wrote:
ERROR: could not convert table b to a view because it has triggers
HINT: In particular, the table cannot be involved in any foreign key
relationships.
** Error **
ERROR: could not convert table b to a view because it has triggers
SQL state: 55000
ERROR: could not convert table b to a view because it has triggers
HINT: In particular, the table cannot be involved in any foreign key
relationships.
** Error **
ERROR: could not convert table b to a view because it has triggers
SQL state: 55000
Hint: In particular,
salah jubeh wrote:
http://www.postgresql.org/docs/current/static/catalog-pg-class.html
relhastriggers boolTrue if table has (or once had) triggers
This is what is queried when you try to convert the table into a view.
So there is no way to convert your table to a view unless you are
salah jubeh wrote:
http://www.postgresql.org/docs/current/static/catalog-pg-class.html
relhastriggers bool True if table has (or once had) triggers
This is what is queried when you try to convert the table into a view.
So there is no way to convert your table to a view unless you are
salah jubeh s_ju...@yahoo.com writes:
create table a (id int primary key);
create table b (id int primary key, a_id int references a (id));
insert into a values (1);
insert into b values (1,1);
create table c AS SELECT * FROM b;
TRUNCATE b;
ALTER TABLE b DROP CONSTRAINT b_a_id_fkey;
Hello Tom,
Patient: Doctor, it hurts when I do this.
Doctor: So, don't do that.
Why would you think this is a good thing to do? Why not just rename
table b to c, and then create the view as b?
(For context, it's not even considered a supported operation to
manually create _RETURN rules like
