If you really mean relational, and not SQL; then all you need is columns, tables and records. Just do it, once you have a stupid implementation of your ideas ru

If you really mean relational, and not SQL; then all you need is columns, tables and records. Just do it, once you have a stupid implementation of your ideas running you'll know what information to look for. I've been cooking my own relational persistence engines for quite a while now, here is the latest incarnation if anyone is interested in seeing the idea cut down to its core with optional encryption on top: https://github.com/andreas-gone-wild/snackis/tree/master/src/snackis/db https://github.com/andreas-gone-wild/snackis/tree/master/src...