agora inbox for pljava-dev@postgresql.org  

help / color / mirror / Atom feed

[Pljava-dev] table level triggers?
2+ messages / 0 participants
[nested] [flat]

* [Pljava-dev] table level triggers?
@ 2005-11-13 03:29 
  2005-11-13 10:04 ` [Pljava-dev] table level triggers? 
  0 siblings, 1 reply; 2+ messages in thread

From:  @ 2005-11-13 03:29 UTC (permalink / raw)

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




^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* [Pljava-dev] table level triggers?
  2005-11-13 03:29 [Pljava-dev] table level triggers? 
@ 2005-11-13 10:04 ` 
  0 siblings, 0 replies; 2+ messages in thread

From:  @ 2005-11-13 10:04 UTC (permalink / raw)

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
>   





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2005-11-13 10:04 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-11-13 03:29 [Pljava-dev] table level triggers? 
2005-11-13 10:04 ` 

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox