I've run two tests today. Both involved inserting lots of rows. One test used many INSERT INTO statements. The other test used INSERT INTO ... SELECT statements that added 1 million rows at a time.
Both successfully added much more than Integer.MAX_VALUE rows. Harish, I guess that means we need you to create a reproducible test case. For the record, in both cases these are the db options I used: LOG=0;CACHE_SIZE=0;LOCK_MODE=0;UNDO_LOG=0 On Wednesday, 4 April 2012 17:23:52 UTC+2, Steve McLeod wrote: > > I don't think increasing the page size is the answer. I've been running a > test with the default page size, inserting batches of 1,000,000 rows at a > time, and it has surpassed Integer.MAX_INT. > > I'll change my test now to use INSERT INTO AS SELECT to see if that > surpasses Integer.MAX_INT > > > > On Wednesday, 4 April 2012 16:47:10 UTC+2, Noel Grandin wrote: >> >> >> Cranking up the page size will probably extend the number of rows you >> can store in a table. >> The default is 2K, I would crank it up to 16K. >> >> -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/cqev81VB7HoJ. 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.
