> it often takes a lot of fiddling to get what you want and yet, for any nontrivial operations, opting for a few simple K:V stores instead means one basically

> it often takes a lot of fiddling to get what you want and yet, for any nontrivial operations, opting for a few simple K:V stores instead means one basically ends up implementing an unrolled SQL engine processing loop to do the application-specific select statements you would otherwise need. there's a reason SQLite took over from dbm files ...