1) Indeed you should only use mmap for reads afaik 2) Was thinking more of an event-sourcing model, whereby you log the SQL statements first, then update a B-T

1) Indeed you should only use mmap for reads afaik 2) Was thinking more of an event-sourcing model, whereby you log the SQL statements first, then update a B-Tree in the background. Read via mmap, write by appending to a log and asynchronously applying the changes to the file. 3) Rather than yet another QL, expose a higher level API that I can target in any language