Hi, > That would allow the Trigger instances to create and cache PreparedStatements in their init() method.
Yes, if you look at the FullTextTrigger class (package org.h2.fulltext), you can already cache the prepared statements, using this system session. Regards, Thomas On Thu, Jul 18, 2013 at 9:13 AM, Noel Grandin <[email protected]> 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. > > -- > 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. > > > -- 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.
