Skip site navigation (1) Skip section navigation (2)

Re: rewriter in updateable views

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: rewriter in updateable views
Date: 2005-03-28 04:12:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sat, 19 Mar 2005 11:42:18 +0000, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I can see that I might want the view to have a different default value
> from that of the underlying table. I can see a reason to have multiple
> updateable views on the same table, all with different columns, column
> defaults and row selection clauses. (Multiple classes all held within
> the same physical table, for example).
> I'd suggest - if the default value for a column on a view IS NOT set,
> then use the default value from the underlying table. If it IS set, then
> it should stay set, even if the underlying table changes. That might
> need some dependency logic in there...
> Best Regards, Simon Riggs
I think i can do this within rewriterHandle.c:build_column_default
immediatly after the first try i can ask if expr == NULL and if is it
a view if  so my code start looking for defaults on base tables maybe
using something like the parse_relation.c:colNameToVar function to
identify the column. there is a better way to do it? also the
ParseState parameter is extensively used in the colNameToVar function
but i can't find what is it.

Jaime Casanova

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-03-28 05:04:01
Subject: Re: locks in CREATE TRIGGER, ADD FK
Previous:From: 윤동수Date: 2005-03-28 03:54:18
Subject: how can I use a bound cursor

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group