Re: Using rules to implement backward-compatible schema changes

From: Mario Becroft <pgsql(at)becroft(dot)co(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mario Becroft <pgsql(at)becroft(dot)co(dot)nz>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Using rules to implement backward-compatible schema changes
Date: 2008-01-01 07:40:09
Message-ID: 87y7baouxy.fsf@server.ak.quickcircuit.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Mario Becroft <pgsql(at)becroft(dot)co(dot)nz> writes:
>> The problem is that when inserting to the view, default values do not
>> work as expected.
>
> You need to attach the defaults to the view, viz
>
> ALTER TABLE a ALTER COLUMN bar SET DEFAULT 5;
>
> This is considered a feature not a bug, since you might want a
> different default for inserts to the view than for inserts
> directly to the underlying table.

This crossed my mind, but I could not find a way of specifying defaults
for a view. I see now that it must be done with ALTER TABLE.

Thanks for your help with this problem.

--
Mario Becroft (postgres-related mail) <pgsql(at)becroft(dot)co(dot)nz>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Louis-David Mitterrand 2008-01-01 14:28:37 Re: EPOCH TIMESTAMP Conversion Problem
Previous Message Tom Lane 2008-01-01 07:09:18 Re: Using rules to implement backward-compatible schema changes