From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | Sarah Officer <officers(at)aries(dot)tucson(dot)saic(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERAL] triggers & functions |
Date: | 2000-01-13 17:26:50 |
Message-ID: | 387E0ADA.CB863926@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Did this help? If not, what was missing? [I'm giving this advice
repeatedly, but not sure it's helping...]
Cheers,
Ed Loehr
Ed Loehr wrote:
> Oh, and one other thing...
>
> The example has a typo. In the function, 'temp' and 'cust' should be the
> same variable (doesn't matter what it's called).
>
> Cheers,
> Ed Loehr
>
> Ed Loehr wrote:
>
> > Sarah Officer wrote:
> >
> > > Can anyone set me straight here? An example of a trigger which
> > > calls a sql procedure would be much appreciated! I'd like the
> > > function to be able to access the rows which are being removed.
> >
> > How about examples of a trigger that calls a *PL/pgSQL* procedure that
> > has access to the rows being removed?
> >
> > http://www.deja.com/getdoc.xp?AN=570616874
> >
> > Oh, and I don't understand the opaque business yet, either. But it
> > seems I must return an opaque type for any function called directly by
> > a trigger, and that OLD and NEW are only available to that function...
> >
> > Cheers,
> > Ed Loehr
>
> ************
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-01-13 17:33:39 | Re: [GENERAL] oid data typeu |
Previous Message | Bruce Momjian | 2000-01-13 17:18:46 | Re: [GENERAL] oid data typeu |