MIME-Version: 1.0
In-Reply-To: <50A40AEB.1020804@femto-st.fr>
References: <50A01024.5010007@femto-st.fr>
	<CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com>
	<50A40AEB.1020804@femto-st.fr>
From: Josh Kupershmidt <schmiddy@gmail.com>
Date: Sun, 13 Jan 2013 14:47:14 -0700
Message-ID: 
 <CAK3UJRH53ikaqRfubJ9sisgX=eTVvQkd40Bq8RwJ9JeEkeYrYQ@mail.gmail.com>
Subject: Re: Incomplete compatibility information for triggers
To: Louis-Claude Canon <louis-claude.canon@femto-st.fr>
Cc: pgsql-docs@postgresql.org
Content-Type: multipart/mixed; boundary=20cf307d0678f1267004d33279cd
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org


--20cf307d0678f1267004d33279cd
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 14, 2012 at 2:19 PM, Louis-Claude Canon
<louis-claude.canon@femto-st.fr> wrote:
> Le 14/11/2012 05:23, Josh Kupershmidt a =E9crit :
>
>> On Sun, Nov 11, 2012 at 3:52 PM, Louis-Claude Canon
>> <louis-claude.canon@femto-st.fr> wrote:
>>
>>> the compatibility section of the "create trigger" page
>>> (http://www.postgresql.org/docs/devel/static/sql-createtrigger.html)
>>> claims
>>> that a missing functionality is the ability to define aliases for the
>>> "old"
>>> and "new" rows or tables. If I am understanding this correctly, another
>>> related missing functionality is that PostgreSQL does not allow the old
>>> and
>>> new tables to be referenced for statement-level triggers (i.e., the "OLD
>>> TABLE" that contains all the deleted/modified rows in case of
>>> deletion/update). I think this is also worth noting as any workaround f=
or
>>> it
>>> seems to be more difficult (if possible at all) than for the missing
>>> alias
>>> 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.

A (belated) +1 for this patch. There were two small typos which I've
fixed in the attached version. You may want to add this patch soon to
the 2013-01 CommitFest so it doesn't get lost.

> By the way, I can propose another patch regarding the transaction isolati=
on
> relatively to my previous post on pgsql-bugs.

If that doc change hasn't been made yet, you may want to post a patch.

Josh

--20cf307d0678f1267004d33279cd
Content-Type: application/octet-stream;
	name="0002-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patch"
Content-Disposition: attachment;
	filename="0002-Document-the-missing-OLD-NEW-TABLE-trigger-feature.patch"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_hbwprzl31

ZGlmZiAtLWdpdCBhL2RvYy9zcmMvc2dtbC9yZWYvY3JlYXRlX3RyaWdnZXIu
c2dtbCBiL2RvYy9zcmMvc2dtbC9yZWYvY3JlYXRlX3RyaWdnZXIuc2dtbApu
ZXcgZmlsZSBtb2RlIDEwMDY0NAppbmRleCAwZjg3YjFmLi40OWE4MTMwCioq
KiBhL2RvYy9zcmMvc2dtbC9yZWYvY3JlYXRlX3RyaWdnZXIuc2dtbAotLS0g
Yi9kb2Mvc3JjL3NnbWwvcmVmL2NyZWF0ZV90cmlnZ2VyLnNnbWwKKioqKioq
KioqKioqKioqIENSRUFURSBUUklHR0VSIHZpZXdfaW5zZXJ0CioqKiA0ODQs
NDk0ICoqKioKICAgIDxwYXJhPgogICAgIFRoZSA8Y29tbWFuZD5DUkVBVEUg
VFJJR0dFUjwvY29tbWFuZD4gc3RhdGVtZW50IGluCiAgICAgPHByb2R1Y3Ru
YW1lPlBvc3RncmVTUUw8L3Byb2R1Y3RuYW1lPiBpbXBsZW1lbnRzIGEgc3Vi
c2V0IG9mIHRoZQohICAgIDxhY3JvbnltPlNRTDwvPiBzdGFuZGFyZC4gVGhl
IGZvbGxvd2luZyBmdW5jdGlvbmFsaXR5IGlzIGN1cnJlbnRseSBtaXNzaW5n
OgogIAogICAgIDxpdGVtaXplZGxpc3Q+CiAgICAgIDxsaXN0aXRlbT4KICAg
ICAgIDxwYXJhPgogICAgICAgIFNRTCBhbGxvd3MgeW91IHRvIGRlZmluZSBh
bGlhc2VzIGZvciB0aGUgPHF1b3RlPm9sZDwvcXVvdGU+CiAgICAgICAgYW5k
IDxxdW90ZT5uZXc8L3F1b3RlPiByb3dzIG9yIHRhYmxlcyBmb3IgdXNlIGlu
IHRoZSBkZWZpbml0aW9uCiAgICAgICAgb2YgdGhlIHRyaWdnZXJlZCBhY3Rp
b24gKGUuZy4sIDxsaXRlcmFsPkNSRUFURSBUUklHR0VSIC4uLiBPTgotLS0g
NDg0LDUwNSAtLS0tCiAgICA8cGFyYT4KICAgICBUaGUgPGNvbW1hbmQ+Q1JF
QVRFIFRSSUdHRVI8L2NvbW1hbmQ+IHN0YXRlbWVudCBpbgogICAgIDxwcm9k
dWN0bmFtZT5Qb3N0Z3JlU1FMPC9wcm9kdWN0bmFtZT4gaW1wbGVtZW50cyBh
IHN1YnNldCBvZiB0aGUKISAgICA8YWNyb255bT5TUUw8Lz4gc3RhbmRhcmQu
IFRoZSBmb2xsb3dpbmcgZnVuY3Rpb25hbGl0aWVzIGFyZSBjdXJyZW50bHkK
ISAgICBtaXNzaW5nOgogIAogICAgIDxpdGVtaXplZGxpc3Q+CiAgICAgIDxs
aXN0aXRlbT4KICAgICAgIDxwYXJhPgorICAgICAgIDxwcm9kdWN0bmFtZT5Q
b3N0Z3JlU1FMPC9wcm9kdWN0bmFtZT4gZG9lcyBub3QgYWxsb3cgdGhlIG9s
ZCBhbmQgbmV3CisgICAgICAgdGFibGVzIHRvIGJlIHJlZmVyZW5jZWQgZm9y
IHN0YXRlbWVudC1sZXZlbCB0cmlnZ2VycyAoaS5lLiwgdGhlIHRhYmxlcwor
ICAgICAgIHRoYXQgY29udGFpbiBhbGwgdGhlIG9sZCBhbmQvb3IgbmV3IHJv
d3MsIHdoaWNoIGFyZSByZWZlcnJlZCB0byBhcworICAgICAgIDxsaXRlcmFs
Pk9MRCBUQUJMRTwvbGl0ZXJhbD4gYW5kIDxsaXRlcmFsPk5FVyBUQUJMRTwv
bGl0ZXJhbD4gaW4gdGhlCisgICAgICAgPGFjcm9ueW0+U1FMPC8+IHN0YW5k
YXJkKS4KKyAgICAgIDwvcGFyYT4KKyAgICAgPC9saXN0aXRlbT4KKyAKKyAg
ICAgPGxpc3RpdGVtPgorICAgICAgPHBhcmE+CiAgICAgICAgU1FMIGFsbG93
cyB5b3UgdG8gZGVmaW5lIGFsaWFzZXMgZm9yIHRoZSA8cXVvdGU+b2xkPC9x
dW90ZT4KICAgICAgICBhbmQgPHF1b3RlPm5ldzwvcXVvdGU+IHJvd3Mgb3Ig
dGFibGVzIGZvciB1c2UgaW4gdGhlIGRlZmluaXRpb24KICAgICAgICBvZiB0
aGUgdHJpZ2dlcmVkIGFjdGlvbiAoZS5nLiwgPGxpdGVyYWw+Q1JFQVRFIFRS
SUdHRVIgLi4uIE9OCg==

--20cf307d0678f1267004d33279cd
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

--20cf307d0678f1267004d33279cd--