From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | alias for OLD and NEW in triggers |
Date: | 2006-06-16 03:20:29 |
Message-ID: | c2d9e70e0606152020y7f251e49te430cc298a957c7b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
i want to make this patch usable
http://archives.postgresql.org/pgsql-patches/2004-12/msg00089.php
as i understand, it needs some refactor, at least plpgsql support,
pg_dump support and docs.
any comments are welcome...
also the autor states this:
> From: hyip ( at ) site ( dot ) uottawa ( dot ) ca
> just want to emphasis one thing.
>
>The point is this implementation is the fundamental, necessary, and
>critical preparation and step for implementing execution of standard SQL
>commands in trigger action in future, instead of using user-defined
>functions in trigger action.
why it's necessary and *critical* for implementing execution of standard SQL
commands in trigger action in future?
maybe i'm very wrong (very possible) but i see this just as make up...
i don't see how say 'old_row' is so different of saying 'OLD'
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-16 03:22:07 | Re: Please help! |
Previous Message | Tom Lane | 2006-06-16 03:17:11 | Re: Tuple hint bits (INFOMASK) upon transaction abort |