From: | thomas at tada(dot)se (Thomas Hallgren) |
---|---|
To: | |
Subject: | [Pljava-dev] table level triggers? |
Date: | 2005-11-13 10:04:20 |
Message-ID: | 43770FA4.9040608@tada.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
Darren,
SQL (and PostgreSQL) implements triggers that are fired 'for each
statement' or 'on each row'. PL/Java implements both. It is impossible
for a PL (any PL) to introduce new types of triggers. Ideas in that
direction is better debated on the PostgreSQL general mailing list. I
suspect however, that the postgresql community will be reluctant to
implement non-standard trigger types.
Kind regards,
Thomas Hallgren
that PostgreSQL has
dgovoni at metadapt.com wrote:
> Hi all,
> Pardons if this topic is located somewhere I have missed or has been
> already discussed, but is there a plan to ever have table-level triggers? My
> understanding is that current triggers fire on rows when an insert,
> update or delete occurs.
> I was thinking it would be nice to have one at the table level (called once
> for each result set on a table) with special attention to before/after
> "reads". This would allow privileged access control mechanisms to be
> developed for tables and pluggable via pljava. I know that there are some
> inside the database already, but with a custom trigger, it could do things
> like call out to a directory or some external resource to determine
> visibility.
>
> Is this even a good idea?
>
> Thank you!
> Darren
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>
From | Date | Subject | |
---|---|---|---|
Next Message | Burtenshaw, John J. | 2005-11-14 13:59:46 | [Pljava-dev] Question regarding triggers and data visibility |
Previous Message | dgovoni at metadapt.com | 2005-11-13 03:29:09 | [Pljava-dev] table level triggers? |