OlegDB
OlegDB copied to clipboard
infoforcefeed
Enough works to use this in production
We need a hero. OlegDB is that hero. I propose we have a new OlegDB Query Language (OTERCAL for obvious reasons which are an exercise best left to the reader)...
We have too many obtuse return codes for various functions. Add an enum thats something like `OLEG_SUCCESS` and `OLEG_FAILURE`. Have all `ol_*` and `olt_*` functions return them. Then, when this...
To repro: 1. Run OlegDB 2. Point `./scripts/torture.py` 3. Wait 4. Watch Oleg segfault
In the beginning there was chaos. Database servers were overbloated, overcomplicated, and fully did a great job of abstracting away the /actual data/ that developers want to see into tables,...
General dumping ground for things that need doing to make Oleg Do the Dew™ faster. - AOL is pretty damn slow right now. [See ticket.](https://github.com/infoforcefeed/OlegDB/issues/87) - `fsync`/`fflush` distinction. I've had...
CUnjar looks pretty clean, but you can watch memory usage slowly creep up if you just keep unjarring the same key over and over again. My go expertise isn't good...
We need some goddamn datatypes. And a query language.