From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(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 14:44:57 |
Message-ID: | c2d9e70e0506060744362ec138@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/6/05, Richard Huxton <dev(at)archonet(dot)com> wrote:
> 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.
>
Actually, i try to do that but i need the function to be polymorphic
and because polymorphic functions needs to receive at least one
polymorphic argument that teach about the return type of the function
i can't go ahead with this idea.
About the code i talk earler in this thread i solve the problem with
the update to serial columns.
--
Atentamente,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2005-06-06 14:48:11 | Re: Solution proposal for TODO item "Clients: sequences" |
Previous Message | Tom Lane | 2005-06-06 14:44:49 | Re: ARRAY() returning NULL instead of ARRAY[] resp. {} |