Hi, > in the case of multiple, in-memory db's with multiple threads accessing them, > would it be useful to give each 'Session' or 'Database' its own Value object > cache?
No, I think that's not required. Values are immutable and independent of the database. > Also, it seems to me (atleast in C++-land) that the 'Value' system to be a > good candidate to put on a memory pool rather than going through new/delete. > Any thoughts on that? Yes, that may be a good idea. The problem is that in C++ there is no garbage collection, so it's harder to re-use the same value in multiple places. Either you use some kind of garbage collection, or you may end up using more memory than the Java version in this case. Probably I would first try without, and only implement a pool / cache when it's really a problem. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. 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.
