Re: TODO item: support triggers on columns - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: TODO item: support triggers on columns
Date
Msg-id 4e8e6eb664ad433f5d179ba231cca045@biglumber.com
Whole thread Raw
In response to Re: TODO item: support triggers on columns  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: TODO item: support triggers on columns
Re: TODO item: support triggers on columns
Re: TODO item: support triggers on columns
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> I'd like to start working on the following TODO item:
> Referential Integrity / Support triggers on columns
>
> Is somebody else already working on this?

Sorry for not jumping in earlier. As Rob said, I am working on
column-level support for triggers. I did not have my name addded
to the TODO list as I wanted to at least get a proof of concept
going first to make sure I could undertake it. I am partway there,
but there are still a lot of rough edges. I guess at this point
I should formally put my name on the TODO, and can bail out if
it gets over my head?

By the way, does anyone know what the tgattr field in pg_triggers
is for? It's allocated but never populated, and would be perfect
for my purposes on this patch, but I don't want to use it if it is
being reserved for something else.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200503121915
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFCM4ZwvJuQZxSWSsgRAhesAKCXi468EyjJ77yMW83Zuoy9glm6XACgxBod
3PZ+l26fRrPY5glMpY+6gxM=
=P+cR
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Andrew - Supernews
Date:
Subject: Re: Bumping libpq version number?
Next
From: Oleg Bartunov
Date:
Subject: Re: REL8_0_STABLE and 8.0.1 release client logging difference