From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Jaime Casanova <systemguards(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Updatable views |
Date: | 2006-08-24 19:08:32 |
Message-ID: | BC7ECC8BDBC7299D9529BC48@[172.26.14.247] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
--On Donnerstag, August 24, 2006 11:02:43 -0500 Jaime Casanova
<systemguards(at)gmail(dot)com> wrote:
> Actually the code delete implicit rules based on a field added to
> pg_rewrite but that catalog has a unique index on ev_class, rulename:
> "pg_rewrite_rel_rulename_index" UNIQUE, btree (ev_class, rulename)
>
> i guess bernd's comment is about this index giving an error if we try
> to insert the new rule with the same name on the same event...
No, this wasn't the problem, since we are going to drop any implicit
rule that collides with an user defined one (however, this approach is
discussable, but nobody has put his comments on this yet and i think this
is important for backwards compatibility). I don't think we need ev_kind in
the
index at all, in my opinion implicit and user defined rules of the same
event
shouldn't live together (_RETURN rules are marked as implicit ones now, too)
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-24 19:17:19 | Re: PL/Perl: spi_prepare() and RETURNING |
Previous Message | Tom Lane | 2006-08-24 19:01:22 | Re: PL/Perl: spi_prepare() and RETURNING |
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2006-08-24 20:25:46 | Re: Updatable views |
Previous Message | Zoltan Boszormenyi | 2006-08-24 18:58:18 | Re: [HACKERS] COPY view |