Clif
See point 6 on my post <grin>
It's not enough on a 24x7 site to just have a wrapper if the name of the
subroutine doesn't change - UniVerse may still cache the object code in memory
if the file is opened e.g. to named common.
So I hold the name of the routine to call externally, and have the master
trigger read it. Then I can vary it when the subroutine changes (e.g. adding a
version number to the end).
Brian
Oooo! Now there's a neat trick (excuse me, "technique"). I'd never
thought of it.
Have you ever used Mark Baldridge's Profiler ("Travels With Mark," on
the IBM Developer Works site) to quantify what I assume is a rather
trivial amount of overhead in the double call? If not, I'll take a go
at it and report back. It sounds like a great technique. Thanks!
--
Regards,
Clif
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678 Web: www.oliver.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Sep 12, 2007, at 8:23 PM, Phil Walker wrote:
> What I do is create a wrapper trigger program which does nothing
> more than call the real subroutine. That way as this trigger never
> or rarely changes I can modify the underlying trigger program
> without having to drop and recreate the trigger on the file.
>
> ---- Clifton Oliver <[EMAIL PROTECTED]> wrote:
>
> =============
> Two more come to mind:
>
> If you change and recompile the subroutine, you have to drop and re-
> create the trigger.
>
> Files with triggers cannot be updated via UV/Net.
>
>
> --
>
> Regards,
>
> Clif
>
>
> On Sep 12, 2007, at 2:04 AM, Brian Leach wrote:
>
>> 5. Triggers impose some limitations : they all make sense if you
>> step back and think about them except (b):
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
