Re: thw rewriter and default values, again

From: Richard Huxton <dev(at)archonet(dot)com>
To: Jaime Casanova <systemguards(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: thw rewriter and default values, again
Date: 2005-06-06 10:16:31
Message-ID: 42A4227F.60902@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova wrote:
> I know you're right, but -when dealing with updateable views- doing
> that implies to add a lot of time altering views when base table
> change, and of course we maybe don't want all views get that values.

Sorry for the late posting on this thread.

Might there be any way to have something like ...SET DEFAULT
pg_same_as('public','foo','col1').

Hmm - you'd need pg_same_as_int/text/etc. depending on the return-type -
still not ideal.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-06-06 13:33:22 Re: lastval()
Previous Message Mark Cave-Ayland 2005-06-06 10:16:17 Re: Quick-and-dirty compression for WAL backup blocks