If there is only 1 instance / 1 trigger (which would be good :)
it does raise the question why are they not implemented as static
methods like functions?
- rami
On 26.5.2010 11:08, Rami Ojares wrote:
My mistake!
The reason why there were 2 instances of every trigger was that
somewhere along the line
they were created also in PUBLIC schema.
So my question is: is there always 1 instance / 1 trigger ?
That would make much more sense considering methods like close() and
remove().
Continuing my investigations...
- rami
On 26.5.2010 10:32, Rami Ojares wrote:
But what I noticed is that more than one instance of a trigger is
created so when the trigger is fired
it is a different instance to which I stored the data.
It seems that two instances of the same trigger are instantiated.
I don't know if the instance count will increase as load increases
but initially there always seems to be 2 instances of every single
trigger.
- rami
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
