> On 10/10/11 11:47, Dimitry Sibiryakov wrote: >> 10.10.2011 9:41, Alex Peshkoff wrote: >>> But telling true I do not think that such game >>> is worth playing - too many conditions should be met. >> It is worth for Oracle because >> a) condition is evaluated in SQL machine and let it avoid switching to >> PL/SQL machine if >> the condition doesn't met. (Such switch is very slow.) >> b) trigger body can be in Java. >> >> Firebird don't have both these problems. >> > > Please take into an account - in FB3 trigger body can also be in Java > (or speaking generally on any language). And this makes me start to > think that WHEN clause may be something useful in that case.
When proposing the WHEN clause, I hadn't support for external languages in mind, but if this means, that the trigger don't need to fire up a virtual environment (e.g. JVM) for external language code execution, then this might be performance improvement. But then it depends on what is necessary that the expression in the WHEN clause can be evaluated. Regards, Thomas ------------------------------------------------------------------------------ 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
