Hi, Without the DIRECT option, the query is first executed completely (rows are read in memory, and possibly buffered to disk if there are many rows), and only after that they are inserted into the table. With the DIRECT option, rows are inserted into the table while executing the query.
Once "server side" cursors are implemented, this distinction is no longer needed (rows are never buffered when using server side cursors). Until then, you can try using the DIRECT option if the default setting are too slow for your. Regards, Thomas On Tue, May 27, 2014 at 1:24 PM, Noel Grandin <[email protected]> wrote: > > > On 2014-05-27 02:35, Brian Craft wrote: > >> >> When using |SORTED|, b-tree pages are split at the insertion point. This >> can improve performance and reduce disk usage. >> > > I don't know what the DIRECT option is up to, but the SORTED option allows > the insertion process to be more efficient because it can assume that the > incoming data is already correctly sorted for the target table. > > > -- > 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/d/optout. > -- 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/d/optout.
