Quinlan Pfiffer

Fits Oleg pretty damn well. I think this is probably blocked by the memory leaks in the frontend, and the better transactions stuff.

Where the hell are we going to get an MS SQL license you fascist? This is codesmell. I will not stand for this intolerable propriety. Edit: And your acronym doesn't...

@Hamcha Wow I guess I never saw your comment, but yeah with the current architecture we should be able to do that.

@Hamcha: That is done [in the transaction branch](https://github.com/infoforcefeed/OlegDB/commit/64117d1671340ec81e857b700f0c4dd184471a7a)

This is now the "Implement Locking" ticket.

@Hamcha: I think it mostly works, except a couple of the tests are hard-coded to expect certain results to be on a 64-bit machine. It'll need some macro wizardry, probably....

Going to do multiple, I think. I'll hold all current committed transactions in a splay tree, and then all transaction commands will require a transaction ID for lookup.

http://www.erlang.org/doc/man/file.html#consult-1

I think this needs to be re-examined. I think compaction is broken right now on large datasets.

@Hamcha Well we were thinking of adding in datatypes. Maybe turning OlegDB into a document store or something like that. I sort of want to write my own BSON/JSONB parser...