Re: Adopted authority and triggers

[Brian <system.i.lists@xxxxxxxxx>]

I was thinking the save/restore would be one of the reasons but
backup/restore procedures have to take triggers into consideration and not
rely on such illusions as that if I put the trigger program in the same
library as the physical file then all will be well when I need to
restore. What if the trigger program is updating a file in a different
library? Having the trigger program in a separate library does not preclude
it from being saved and restored at the same time the physical file is
restored.

Here, the data objects for an application are in one library and the objects
that act on that data, including trigger programs, are stored in a
different library. One user profile owns all the objects and is the only
profile that has authority to the data objects; users are given authority to
programs which adopt authority as necessary. Using this method, the problem
Roger is having with his trigger program is a non-issue.

Hmm, I never have thought of a trigger program as part of the database. It
is linked to the database but is it really a part of it?





On 4/4/07, Ed Fishel <edfishel@xxxxxxxxxx> wrote

I am a security guy and not a data base guy. My understanding is that a
> trigger program is part of the data base. It should be saved and restored
> with the data base, copied with the data base, etc. (There is probably
> more
> to it that these reasons.)  With this in mind it makes sense that a user
> should not need authority to the trigger program or its library. The
> system
> should always be able to call the trigger program when the user is
> authorized to open the file.
>
> Ed Fishel,
> edfishel@xxxxxxxxxx