Subject | Re: [Firebird-Architect] Database triggers |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2006-09-20T00:04:31Z |
Vlad Horsun wrote:
But anyway if someone wants to reject a logon in AFTER CONNECT but
logging, he could use a external table.
Or AFAIU, "autonomous transaction" could be used.
Adriano
>>>> This would be a very starting point for virtual tables. Rather thanTotally agreed.
>>>>
>>>> What account do the trigger run under?
>>>>
>>> Under account of user who initiated action. All proposed triggers
>>> fired at moment where valid user account is established
>>>
>> That really won't work for before connect or after disconnect triggers.
>>
>
>
> Are we realy need such triggers ?
>
> Before connect we don't know who tried to connect as user credentials
> not verified. After disconnect have no more info then before disconnect -
> only status of successful disconnection. Both this triggers have no established
> attachment so we can't do something in database within it.
> Therefore i see no value in such triggers ;)
>
> I can be wrong here, of course
>
But anyway if someone wants to reject a logon in AFTER CONNECT but
logging, he could use a external table.
Or AFAIU, "autonomous transaction" could be used.
Adriano