From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Names of view select rules |
Date: | 2002-04-18 22:29:25 |
Message-ID: | 200204182229.g3IMTPY15119@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
No problem with that. Good idea IMHO.
Jan
Tom Lane wrote:
> Currently, the name of the ON SELECT rule for a view is defined to be
> '_RET' || viewname
> truncated if necessary to fit in a NAME.
>
> I've just committed fixes to make rule names be per-relation instead
> of global, and it occurs to me that we could now get rid of this
> convention. The select rule name could be the same for all views ---
> "_RETURN", say. This would simplify life in a number of places.
>
> A quick look at psql, pgaccess, etc suggests that a lot of places know
> that view select rule names begin with _RET, but not that many are
> dependent on the rest of it. So I think this wouldn't break clients
> too badly.
>
> Any thoughts pro or con? I'm leaning towards changing it, but could be
> persuaded to leave well enough alone.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Nicolas Bazin | 2002-04-18 22:53:59 | Re: [HACKERS] build of 7.2.1 on SCO Openserver andUnixware |
Previous Message | Mark Pritchard | 2002-04-18 21:41:47 | Re: Index Scans become Seq Scans after VACUUM ANALYSE |