I would try something like: SELECT NEXT VALUE FOR xxx, NEXT VALUE FOR xxx, NEXT VALUE FOR xxx, etc
And then profile and see where the bottleneck is. You can also try modifying the CACHE value for a sequence to limit how often it gets synched to disk. On 2014-05-25 04:10, Brian Craft wrote:
In larger dbs, the limiting operation for large inserts is allocating sequence values for the primary key. What's a good strategy for allocating sequence values in bulk? Only a single thread updates the db, so there's no concern of values being allocated elsewhere during the inserts.
-- 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.
