Harish, This sounds suspiciously like a case of internally or externally using a signed type instead of an unsigned type...The range of integers in Java is 2^64...but half of those are negative...and you are getting close to 2^32 rows in your table before the problem.
I guess Thomas will be on to this quickly, but I'm curious about this problem and want to look into it myself too. Can you post some simple code that reproduces this? Eg, Java code to create and populate a table with only one or two columns. Regards, Steve On Tuesday, 3 April 2012 22:31:40 UTC+2, Harish Mahadevan wrote: > > Hi Guys, > > A recent update on this issue is, i got the job to do a very timely commit > and it is fast, but after running it multiple times for testing and > validation found something very interesting. > The inserts were working really well until the table had 2147483647 > (Integer.MAX_LIMIT) number of records, the inserts were happening at a very > constant speed of 60,000,000 every 10 mins roughly with a commit size of 2 > million. After the job inserts 2147483647 records into the table the job > doesn't do anymore. I have ran the job more than 5 times and have noticed > it gets to the same exact size every single time. I would like to know if > h2 uses the Integer.MAX_SIZE for any of the row size calculation or > something like that. Because I read on the limits and limitation of h2 that > a single table could have 2^64 rows. So it would be helpful if someone > could explain more on this issue. > > Thanks a lot. > > regards > Harish > > > > -- 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/-/RZzo2iyfcg4J. 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.
