Re: SELECTs inside of VIEWs (WAS: INSTEAD OF trigger on VIEWs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jan B(dot)" <jan(at)monso(dot)de>
Cc: Russell Smith <mr-russ(at)pws(dot)com(dot)au>, "--= Tono =--" <tonodarmodjo(at)yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECTs inside of VIEWs (WAS: INSTEAD OF trigger on VIEWs)
Date: 2005-05-24 14:27:36
Message-ID: 20525.1116944856@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jan B." <jan(at)monso(dot)de> writes:
> Does anyone know, if it is intended that one query can create multiple
> result tables with some of them carrying an empty string as cmdStatus?
> Perhaps this is a bug?

Yes it is, and no it isn't. Check the archives --- there was extensive
discussion of what multi-command rules should return, a couple years
back when we settled on the current behavior.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gaetano Mendola 2005-05-24 15:38:04 Re: 8.0.x RPM issues
Previous Message Jeff Eckermann 2005-05-24 14:00:21 Re: SELECTs inside of VIEWs (WAS: INSTEAD OF trigger on VIEWs)