Re: PostgreSQL clustering VS MySQL clustering - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: PostgreSQL clustering VS MySQL clustering
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3412A75CF@Herge.rcsinc.local
Whole thread Raw
In response to PostgreSQL clustering VS MySQL clustering  (Hervé Piedvache <herve@elma.fr>)
List pgsql-performance
> >Technically, you can also set up a rule to do things on a select with
DO
> >ALSO. However putting update statements in there would be considered
(at
> >least by me) very bad form.  Note that this is not a trigger because
it
> >does not operate at the row level [I know you knew that already :-)].
> >
> >
> >
> Unfortunately, you can't.  Select operations only allow a single rule,
> and it must be a DO INSTEAD rule, unless this has changed in 8.0 and I
> missed it in the docs.  However, you can do this in a view by calling
a
> function either in the row definition or in the where clause.

You're right...forgot about that.  Heh, the do instead rule could be a
set returning function which could (besides returning the set) do almost
anything!  So in theory it makes no difference...diclaimer: never tried
doing this!

Merlin


pgsql-performance by date:

Previous
From: Marty Scholes
Date:
Subject: Re: PostgreSQL clustering VS MySQL clustering
Next
From: Marty Scholes
Date:
Subject: Re: PostgreSQL vs. Oracle vs. Microsoft