From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au> |
Cc: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: current is broken |
Date: | 2000-09-15 02:36:16 |
Message-ID: | 001001c01ebd$b8ebfea0$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> > The only thing that's missing is a 'rulekind' for rules - it
> would be very
> > nice if pg_dump could use a simple method (that didn't involve munging
> > names) to determin is a rule is a 'view rule'.
>
> Oh, I finally see the problem: when you come to dump out the rules, you
> need to avoid dumping the rules that correspond to views because you're
> going to emit the CREATE VIEW commands separately.
>
> You don't really need a rulekind though. If it's an ON SELECT rule for
> a relation that you've determined to be a view, then the rule is a
> view rule. Otherwise, you print the rule.
>
Is it guaranteed that ON SELECT rule is unique per view in the future ?
Regards.
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-09-15 02:44:52 | RE: current is broken |
Previous Message | Tom Lane | 2000-09-15 02:23:12 | Re: current is broken |