Re: calling function from rule

From: "Tambet Matiisen" <t(dot)matiisen(at)aprote(dot)ee>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: calling function from rule
Date: 2003-01-24 08:39:26
Message-ID: 81132473206F3A46A72BD6116E1A06AE3EC047@black.aprote.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Thursday, January 23, 2003 7:01 PM
> To: Tambet Matiisen
> Cc: pgsql-sql(at)postgresql(dot)org
> Subject: Re: [SQL] calling function from rule
>
>
> "Tambet Matiisen" <t(dot)matiisen(at)aprote(dot)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

Browse pgsql-sql by date

  From Date Subject
Next Message David Durst 2003-01-24 08:45:38 Re: Scheduling Events?
Previous Message Seethalakshmi VB 2003-01-24 08:36:31 Creating tables from within functions