We should either
(a) throw an exception if the cache size is so big we can't handle it
(b) use BigInteger or store the cache sizes in kilobytes or megabytes to avoid
overflow.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from
Thanks Noel, Andrei,
The cache is split into 16 Segments each segment tracks memory used
and Max cache size using longs.
Looking at the code the overflow would happen if the size of a page or an
Value is over 2GB, the memory used is stored as an in - or in the case of
a page
if two Value
