Hash: SHA1

On Thu, 29 Nov 2007 00:55:53 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:

> David Fetter <[EMAIL PROTECTED]> writes:
> > On Wed, Nov 28, 2007 at 09:58:26PM -0500, Jonah H. Harris wrote:
> >> On Nov 28, 2007 3:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> >>> Entirely removing the example of how to do it with rules doesn't
> >>> seem like a good idea.
> >> 
> >> Agreed.
> > Do you have an example of one use case where using RULEs rather than
> > TRIGGERs is a good idea?
> The argument I made for keeping the example around is not dependent on
> the assumption that using a rule is a good idea.  It's dependent on
> the established fact that we have recommended that in prior releases,
> and therefore people are going to be seeing that construct in real
> databases.

And they could refer back to the older version of the documentation for
it. In fact, we should mention that in the patch:

<note><para>If you have an partitioning setup that uses rules please
refer to the 8.2 documentation on partitioning</para></note>


Joshua D. Drake

>                       regards, tom lane
> ---------------------------(end of
> broadcast)--------------------------- TIP 4: Have you searched our
> list archives?
>                http://archives.postgresql.org

- -- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997  http://www.commandprompt.com/
                        UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

Version: GnuPG v1.4.6 (GNU/Linux)


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to