Subject | Re: Java Routines (was Re: [Firebird-Architect] Re: External Engines (and Plugins)) |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2008-06-25T18:13:10Z |
Roman Rokytskyy escreveu:
TLS but not have it for trigger. And I think this because I believe
FirebirdTriggerContext should be inherited from FirebirdContext (with
generic useful things).
But as trigger can do nothing good without that info, it should be
passed as parameter for it.
Adriano
>>> c) the method declaration is very simple, e.g.:I think it don't make much sense to have function and procedure info in
>>>
>>> public static void
>>> myLoggingTrigger(org.firebirdsql.jdbc.FirebirdTriggerContext ctx) {
>>> someLog.debug("Trigger for table " + ctx.getTableName() + " action
>>> " ...);
>>> }
>>>
>> Such interface is also useful for procedures and functions. So I think
>> is better to put it in TLS, but require it in method parameter (as in
>> your example) for triggers.
>>
>
> Hmmm... why do we need table name, new. and old. contexts in normal code
> via TLS?
TLS but not have it for trigger. And I think this because I believe
FirebirdTriggerContext should be inherited from FirebirdContext (with
generic useful things).
But as trigger can do nothing good without that info, it should be
passed as parameter for it.
Adriano