On 18/07/2013 3:13 AM, Noel Grandin wrote:
On 2013-07-17 19:51, cowwoc wrote:
I am referring to the fact that currently if I want to process N
rows, you need to create N * PreparedStatements (one per row inside
fire()) as opposed to once at the beginning of the transaction. You
are right that this needs to be benchmarked.
One change we could make right now without even having a new
interface, would be to instantiate the Trigger objects on a
per-connection basis.
That would allow the Trigger instances to create and cache
PreparedStatements in their init() method.
While technically speaking you could do so, practically speaking it
isn't clear what impact this would have on implementations in the wild.
The current interface states that init() provides a system connection.
By changing the implementation you would be violating the contract of
the original interface, though again it's not clear whether existing
code would break.
Gili
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
