[EMAIL PROTECTED] writes:
> Below were the communications between Tom and me before I implemented this
> project. I just did what he asked me to do.
Part of it, maybe --- my point was that without any support in (at
least) plpgsql, the feature is of only academic interest. There's not
a lot of p
[EMAIL PROTECTED] wrote:
> > I must be missing something, but AFAICS this patch doesn't actually *do*
> > anything useful. It looks to me like you've implemented a write-only
> > addition to the system catalogs. (And not even done a very good job of
> > that --- no documentation, no pg_dump suppo
I really appreciate that, Mr. Momjian.
>
> This has been saved for the 8.1 release:
>
> http:/momjian.postgresql.org/cgi-bin/pgpatches2
>
> ---
>
> [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> The attached patch adds the option
Thanks, Tom.
1. If you remembered, before I implemented this new feature, I did discuss
with you. Please refer the following emails.
Original Message
Subject: Re: Referencing OLD/NEW Rows on Trigger Definition
From:"Tom Lane" <[EMAIL
> I must be missing something, but AFAICS this patch doesn't actually *do*
> anything useful. It looks to me like you've implemented a write-only
> addition to the system catalogs. (And not even done a very good job of
> that --- no documentation, no pg_dump support.) What's the point?
I just w
[EMAIL PROTECTED] writes:
> The attached patch adds the optional REFERENCES syntax in CREATE TRIGGER
> statement to make an automatic alias for OLD/NEW record during trigger
> setup. The implementation of this new feature makes CREATE TRIGGER
> command more compatible to SQL standard, and allows t
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
[EMAIL PROTECTED] wrote:
> Hi,
>
> The attached patch adds the optional REFERENCES syntax in CREATE TRIGGER
> statement t