From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Tambet Matiisen" <t(dot)matiisen(at)aprote(dot)ee> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: calling function from rule |
Date: | 2003-01-23 17:00:52 |
Message-ID: | 26610.1043341252@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-23 17:21:39 | Re: To use a VIEW or not to use a View..... |
Previous Message | Stephan Szabo | 2003-01-23 16:53:53 | Re: To use a VIEW or not to use a View..... |