I'm currently working on a master student research project "support triggers
on columns" that is supervised by a professor from my university (Ottawa U).
I have contacted Neil Conway whose name is with this item on the TODO list.
It happened that he actually lives very close to me(Queen's U in Kingston).
He has agreed that I work on this.
Please take a look of my design (Some of the ideas are from Neil)

- change gram.y for CREATE TRIGGER to support the optional column list for
this feature,
- change CreateTrigStmt, trigger, trigdesc node to add support for an
optional List of columns; change the various Node  support functions
(equalfuncs.c, copyfuncs.c, etc.)
- change InsertTrigger, (Copy+Free+ equal)TriggerDesc, Relationbuild
function to add support an optional List of columns.
- change the pg_trigger system catalog to support the new column .
- change CreateTrigger() to perform some semantic analysis on the list of
columns (ensure no column names are duplicated,  ensure each name references
an extent and non-dropped column, and so forth)
- when deciding which triggers to invoke (executePlan() in execMain.c), add
logic to compare the list of columns in the  to-be-executed command with the
list of columns in any applicable columns,and only fire a trigger of the
column lists  that are appropriately compatible
-investigate the interaction between the column list and rules

I have spent the past four months on this and I have finished the YYpaser,
Catalog, trigger creation and some other support functions, I am working on
trigger execution right now. I expect the project will be completed by the
end of July. I would like to know your comments on my design and the
procedure of getting my work accepted.

Thanks
Mark Wu

 













I'm
currently working on a master student research project “support triggers on
columns” that is supervised by a professor from my university (Ottawa U). 
I have contacted Neil Conway whose name is with this item on the TODO list. It
happened that he actually lives very close to me(Queen's U in Kingston). He has agreed that I work on this.
Please take a look of my design (Some of the ideas are from Neil)

- change gram.y for CREATE TRIGGER to support the optional column list for this
feature,
- change CreateTrigStmt, trigger, trigdesc node to add support for an optional
List of columns; change the various Node  support functions (equalfuncs.c,
copyfuncs.c, etc.)
- change InsertTrigger, (Copy+Free+ equal)TriggerDesc, Relationbuild function
to add support an optional List of columns.
- change the pg_trigger system catalog to support the new column .
- change CreateTrigger() to perform some semantic analysis on the list of
columns (ensure no column names are duplicated,  ensure each name
references an extent and non-dropped column, and so forth)
- when deciding which triggers to invoke (executePlan() in execMain.c), add
logic to compare the list of columns in the  to-be-executed command with
the list of columns in any applicable columns,and only fire a trigger of the
column lists  that are appropriately compatible
-investigate the interaction between the column list and rules
I have spent
the past four months on this and I have finished the YYpaser, Catalog, trigger
creation and some other support functions, I am working on trigger execution
right now. I expect the project will be completed by the end of July. I would
like to know your comments on my design and the procedure of getting my work
accepted.

Thanks
Mark Wu
Thu, 1 Jul 2004 19:38:19 -0400
"Mark Wu" <mark.wu@rogers.com>
working on support triggers on columns
On Thu, Jul 01, 2004 at 07:38:19PM -0400, Mark Wu wrote:

> I have spent the past four months on this and I have finished the YYpaser,
> Catalog, trigger creation and some other support functions, I am working on
> trigger execution right now. I expect the project will be completed by the
> end of July. I would like to know your comments on my design and the
> procedure of getting my work accepted.

You could submit a patch to the pgsql-patches list so we can see what
you have actually done.  Since you already have a patch, this may be the
best course of action.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
FOO MANE PADME HUM

Thu, 8 Jul 2004 15:07:51 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl>
Re: working on support triggers on columns

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
 
Mark Wu wrote on July 8, 2004:
> I have spent the past four months on this and I have finished the
> YYpaser, Catalog, trigger creation and some other support functions, I
> am working on trigger execution right now. I expect the project will be
> completed by the end of July. I would like to know your comments on my
> design and the procedure of getting my work accepted.
 
Any update on this? If you are no longer working on this, please let us
know. If not, please send what you already have in so we can work on it
and possibly get it added in to 8.1.
 
Thanks,
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200501282317
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
 
-----BEGIN PGP SIGNATURE-----
 
iD8DBQFB+w6wvJuQZxSWSsgRAr8dAKDGfpxUaqMaJr/Az0MBWQMvBc6IWQCgrZvH
U2bNlnmWVYDgk3nSzL1Bil8=
=5xZJ
-----END PGP SIGNATURE-----



Sat, 29 Jan 2005 04:20:04 -0000
"Greg Sabino Mullane" <greg@turnstep.com>
Re: working on support triggers on columns