Hi,
> This does not seem to be the case though...
You are right, thanks for the test case! Obviously I forgot why the
code is like that. I should have documented it better... I think I
remember now why all delete entries need to be written first:
Because delete entries are always 1 block, while not-deleted entries
can be many blocks. So for example:
(A) block: 1 (delete)
(B) block: 2 (delete)
(C) block: 1 ('Hello', 2 blocks long - so actually block 1+2)
Needs to be written in this order and not (A) (C) (B). I will document
this description.
I know my solution is not optimal, but I thought recovery is not a big
performance problem. Looks like it is a problem for flash drives...
But still I believe implementing a buffering file system is probably a
better solution because it will improve performance for all
operations, not just for recovery. What do you think?
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
-~----------~----~----~----~------~----~------~--~---
