Re: alter table impact on view - Mailing list pgsql-general

From David Rowley
Subject Re: alter table impact on view
Date
Msg-id CAApHDvorxExKAWyKL_FzvN6_j+CXua2OwkpYWq9OCZnxEgq2vQ@mail.gmail.com
Whole thread Raw
In response to alter table impact on view  (Marc Millas <marc.millas@mokadb.com>)
Responses Re: alter table impact on view
List pgsql-general
On Tue, 31 Jan 2023 at 01:14, Marc Millas <marc.millas@mokadb.com> wrote:
> But if I alter table to change a column that is a varchar 20 into a varchar 21
> postgres refuse saying that it cannot due to the return rule... using said column
>
> why ?? as the view is not a materialized object, the impact of the length of a column of an underlying table do
changethe description of the view, clearly, but I dont see where the difficulty is "hidden". Can someone enlighten me?
 

Primarily because nobody has written the required code.

In [1], which is now quite old, there was some discussion about
various aspects of making this better. Perhaps changing the typmod is
easier than changing the type completely, but we still don't have any
code for it. So for now, you're just stuck manually dropping and
recreating your views.

David

[1] https://www.postgresql.org/message-id/603c8f070807291912x37412373q7cd7dc36dd55a8a7@mail.gmail.com



pgsql-general by date:

Previous
From: Marc Millas
Date:
Subject: alter table impact on view
Next
From: Ron
Date:
Subject: Re: How to control pg_catalog results for each users?