Subject | Re: [firebird-support] Re: Maintain Summary Table with Database Trigger |
---|---|
Author | unordained |
Post date | 2010-07-25T00:40:55Z |
---------- Original Message -----------
Besides USER_TRANSACTION, there's also USER_SESSION, which lasts past commit. See
http://www.firebirdsql.org/refdocs/langrefupd20-set-context.html for details.
Instead of trying to replace the status field with a context variable, maybe a
table (not temporary) to store items that need refreshing would suit you better?
-Philip
> If there was a longer term one, it might------- End of Original Message -------
> also eliminate the need for the field in the status table but I will
> definitely make use of it as it is.
Besides USER_TRANSACTION, there's also USER_SESSION, which lasts past commit. See
http://www.firebirdsql.org/refdocs/langrefupd20-set-context.html for details.
Instead of trying to replace the status field with a context variable, maybe a
table (not temporary) to store items that need refreshing would suit you better?
-Philip