Hi, > Will the new "page store" file format lead to smaller database files,
Yes, that's the plan. Plus empty space should be re-used more quickly. My plan is to only create one database file by default (plus the temporary .lock.db file, and maybe other temporary files). > and to smaller memory space requirements for in-memory databases? No, except when using the undocumented in-memory file system (jdbc:h2:memFS:test and the compressed jdbc:h2:memLZF:test). > Will it also support clustered indexes, i.e. that table rows can be > stored physically sorted along the primary key? Yes, that's the plan; but probably only for 'single column primary keys'. Unlike now, tables are organized as a b-tree using a 'int' key. The whole storage format is similar to SQLite, except that SQLite uses only undo logs. But it doesn't make sense to document the details right now because it's work in progress. Unless, of course, if somebody wants to help me implement it :-) > Do you have a rough estimate of when a first alpha version could be ready? It's probably better not to estimate :-) My first estimate was March, but then I found some rather large problems and had to change a lot. Lately I didn't work on it because other issues are more important. 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 -~----------~----~----~----~------~----~------~--~---
