Skip site navigation (1) Skip section navigation (2)

Re: working on support triggers on columns

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Mark Wu <mark(dot)wu(at)rogers(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: working on support triggers on columns
Date: 2004-07-02 21:03:19
Message-ID: 1088802199.30981.402.camel@camel (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, 2004-06-28 at 22:21, Mark Wu wrote:
> 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

Just to clarify, will the column based triggers be settable once per row
or once per statement or both?  will they have access to NEW/OLD data in
the column?  

> 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.

once you have a working patch, post it to pgsql-patches. if it is not
against cvs head make sure you state which branch it is against and that
the patch is for review and after that you'll probably need to begin
work on getting it to work with cvs head at that time (note we will be
in the middle of beta for 7.5 at that point). If it is against cvs head
then just expect to get some feedback on things to clean up. 

oh, and if you haven't already, check out

Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2004-07-02 21:30:49
Subject: Re: Nested Transactions, Abort All
Previous:From: Hannu KrosingDate: 2004-07-02 20:41:06
Subject: Re: Adding column comment to information_schema.columns

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group