From: | Nicklas Avén <nicklas(dot)aven(at)jordogskog(dot)no> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | ERROR: cannot convert relation containing dropped columns to view |
Date: | 2016-02-22 21:30:04 |
Message-ID: | 1456176604.17219.9.camel@jordogskog.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
I get this error message :
ERROR: cannot convert relation containing dropped columns to view
I have googled, but find only very old posts that doesn't seem to be the
same situation.
What I have done is that I have a quite big table that I added a column
to for deletion time.
Then I droped that column and added it again with the right type.
After that I cannot create a rule that is returning data.
The reason I have to return data is irrelevant here, but PostgREST
expects that.
To reproduce:
create table foo
(
id serial,
deleted int
);
alter table foo drop column deleted;
alter table foo add column deleted timestamp;
CREATE or replace RULE del_post AS ON DELETE TO foo
DO INSTEAD
update foo set deleted = now()
WHERE id = OLD.id
returning *;
returns:
ERROR: cannot convert relation containing dropped columns to view
If I don't drop any column (adding the right type at once) it works as
expected.
two questions:
1) is this a bug
2) is there a way to "cean" the table from the deleted columns without
recreating it?
Best Regards
Nicklas Avén
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2016-02-22 21:30:57 | Re: Read-only tables to avoid row visibility check |
Previous Message | Alban Hertroys | 2016-02-22 20:54:04 | Re: Why does query planner choose slower BitmapAnd ? |