Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TYkND-0000KF-Hj for pgsql-docs@postgresql.org; Wed, 14 Nov 2012 21:19:51 +0000 Received: from lifc.univ-fcomte.fr ([194.57.88.66] helo=lifc-proxy.univ-fcomte.fr) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TYkN8-00042z-SX for pgsql-docs@postgresql.org; Wed, 14 Nov 2012 21:19:51 +0000 Received: from [192.168.0.10] (stp25-1-82-226-151-110.fbx.proxad.net [82.226.151.110]) (authenticated bits=0) by lifc-proxy.univ-fcomte.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id qAELJiaK002831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Nov 2012 22:19:44 +0100 Message-ID: <50A40AEB.1020804@femto-st.fr> Date: Wed, 14 Nov 2012 22:19:39 +0100 From: Louis-Claude Canon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: Josh Kupershmidt CC: pgsql-docs@postgresql.org Subject: Re: Incomplete compatibility information for triggers References: <50A01024.5010007@femto-st.fr> In-Reply-To: Content-Type: multipart/mixed; boundary="------------050007090408010605010600" X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201211/11 X-Sequence-Number: 7503 This is a multi-part message in MIME format. --------------050007090408010605010600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by lifc-proxy.univ-fcomte.fr id qAELJiaK002831 Le 14/11/2012 05:23, Josh Kupershmidt a =E9crit : > On Sun, Nov 11, 2012 at 3:52 PM, Louis-Claude Canon > wrote: > >> the compatibility section of the "create trigger" page >> (http://www.postgresql.org/docs/devel/static/sql-createtrigger.html) c= laims >> that a missing functionality is the ability to define aliases for the = "old" >> and "new" rows or tables. If I am understanding this correctly, anothe= r >> related missing functionality is that PostgreSQL does not allow the ol= d and >> new tables to be referenced for statement-level triggers (i.e., the "O= LD >> TABLE" that contains all the deleted/modified rows in case of >> deletion/update). I think this is also worth noting as any workaround = for it >> seems to be more difficult (if possible at all) than for the missing a= lias >> feature. > +1, it seems like a useful missing piece from the SQL:2011 standard. > Care to send a documentation patch? Let me know if it requires a second round. By the way, I can propose another patch regarding the transaction=20 isolation relatively to my previous post on pgsql-bugs. Louis --------------050007090408010605010600 Content-Type: text/x-patch; name="0001-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patch" Content-Disposition: attachment; filename*0="0001-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patc"; filename*1="h" Content-Transfer-Encoding: 7bit --------------050007090408010605010600--