It's easy enough to find a reference
implementation of a B+Tree and re-implement it; as long as we've
thought through all the tradeoffs (I think Henrik made this point).
Speaking of which, I think the Right Thing is developing the B+Tree
library separately from Elephant, so others will be able t
> The quad-tree is definitely not a B+Tree, nor one that solves any of
> the issues of writing to disk.
Well, so much for superficial research. Sorry.
> It's easy enough to find a reference
> implementation of a B+Tree and re-implement it; as long as we've
> thought through all the tradeoffs (I
