NeoDatis ODB

I don't know how to vote for issues in SourceForge, but consider this a +1
vote. In my opinion it's vital for the DB to reclaim deleted blocks
on-the-fly (to prevent needless growth) and provide a means to compact
database files after one-time events involving a large number of inserts
and deletes (resulting in a large number of deleted objects that will never
be fully reused).

Important classes to look at:

ObjectWriter
- protected int markAsDeleted(long currentPosition, OID oid, boolean
writeInTransaction) throws IOException
- protected void storeFreeSpace(long currentPosition, int blockSize)

Things to check/define:
- Check if block size of an object can be computed before storing the
object. Because this size will be used to search for available (deleted)
spaces
- What is the best/fastest way to store/search information about the
deleted blocks.

Logged In: NO

Some issues to think about:

- The delete should organize the information on a list in a fast way
- The delete should search the correct/better position in a fast way
- The delete should be an expert to know identify when it is marking
objects that are "neighbor", optimizing space to the insert and update