|
|
 | | From: | Merlin Moncure | | Subject: | Re: PostgreSQL clustering VS MySQL clustering | | Date: | Fri, 21 Jan 2005 14:23:24 -0500 |
|
|
 | > >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
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
|
|
|
