Hello, Thomas.
As I understood for now H2 don't support real memory tables - MEMORY
modifier makes inmemory
only indexes of table. May be for such case it will be more logical
and flexible to make MEMORY
modifier separately for indexes like CREATE MEMORY INDEX ... and when
such modifier used with
table then keep all table data in memory (and indexes automatically
too) to have no overhead
of hdd io. For data intensive applications for tables with small data
size when persistence not needed
it will be very good idea. In other cases developer will decide it
himself what to keep in memory and
what on hdd for each table and index.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
