> 10.10.2011 12:26, Vlad Khorsun wrote:
>
>> If such clause is inside trigger code then it not affects security checks and
>> *whole* trigger code is checked. SQL standard says something about security
>> checks for conditional triggers ?
>
> I believe the rules are the same. In general, it's impossible to
> evaluate the trigger condition at the prepare time (it can refer to the
> fields of the current record), so I strongly believe we shouldn't even
> try doing that.
>
> So IMO this feature is not going to affect the body parsing and
> permission checking.
Exactly.
And we still must load all active PSQL triggers despite of any declared
condition.
Seems conditional triggers have sence only for external (non-PSQL) triggers.
Regards,
Vlad
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
