Subject | Re: Maintain Summary Table with Database Trigger |
---|---|
Author | JackR |
Post date | 2010-07-23T23:12:53Z |
No kidding?!
Well that IS new stuff to me. I will read up on rdb$get_context(). That's a nice feature.
Thanks for the explanation.
Jack
Well that IS new stuff to me. I will read up on rdb$get_context(). That's a nice feature.
Thanks for the explanation.
Jack
--- In firebird-support@yahoogroups.com, "unordained" <unordained_00@...> wrote:
>
> ---------- Original Message -----------
> From: "JackR" <jack@...>
> > In my
> > program, before making a mass insert, update or delete, I will set the
> > triggers to INACTIVE and then set the field in the status table at
> > then end of processing. Rebuilding the summary table will then happen
> > the next time the data is needed. How can I use a context variable to
> > better accomplish my purpose?
> ------- End of Original Message -------
>
> Oh, that. I misunderstood Vlad, then. I now think he was telling you this would
> be better than activating/deactivating triggers:
>
> create trigger ... as
> begin
> if (rdb$get_context('USER_TRANSACTION', 'notrigger') = '1') then exit;
> ...
> end
>
> Before doing mass updates,
>
> execute block as
> begin
> rdb$set_context('USER_TRANSACTION', 'notrigger', '1');
> end
>
> -Philip
>