Re: calling function from rule - Mailing list pgsql-sql

From Tambet Matiisen
Subject Re: calling function from rule
Date
Msg-id 81132473206F3A46A72BD6116E1A06AE3EC047@black.aprote.com
Whole thread Raw
In response to calling function from rule  ("Tambet Matiisen" <t.matiisen@aprote.ee>)
List pgsql-sql

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, January 23, 2003 7:01 PM
> To: Tambet Matiisen
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] calling function from rule
>
>
> "Tambet Matiisen" <t.matiisen@aprote.ee> writes:
> >> Try 7.3, we changed the rules about returned records count.
>
> > I have 7.3. When rule and action are the same, everything
> works fine.
> > Doing an insert in update rule and opposite are OK too. Problem is,
> > when I do select in insert/update/delete rule. Then the result of
> > select is returned instead of command status, even if the select
> > is done in non-instead rule and there is unconditional instead rule.
>
> Oh, I think your complaint is really about the fact that psql doesn't
> print the command status if it got any tuples (or even just a tuple
> descriptor) in the result series.  AFAICT the information returned by
> the backend is sensible in this situation: the "UPDATE 1"
> status message
> *is* returned and is available from PQcmdStatus.  psql is
> just choosing
> not to print it.  I'm not sure that that's wrong, though.
>

Thanks, I only tested it with psql and got worried.
 Tambet


pgsql-sql by date:

Previous
From: "David Durst"
Date:
Subject: Re: Scheduling Events?
Next
From: Achilleus Mantzios
Date:
Subject: Re: Scheduling Events?