Re: alter table impact on view

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Marc Millas <marc(dot)millas(at)mokadb(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: alter table impact on view
Date: 2023-01-30 12:52:51
Message-ID: CAApHDvorxExKAWyKL_FzvN6_j+CXua2OwkpYWq9OCZnxEgq2vQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 31 Jan 2023 at 01:14, Marc Millas <marc(dot)millas(at)mokadb(dot)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 change the 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2023-01-30 13:18:35 Re: How to control pg_catalog results for each users?
Previous Message Marc Millas 2023-01-30 12:13:58 alter table impact on view