Jun 27, 2026

Completed a database generalization that allows a set of mmaps (files) to be defined and configured as one set, while retaining fluent names to navigate to the individual files. So the set abstraction can hide the distinction for nearly all of the overhead, while keeping the detail is conveniently accessible. Did the same for tables that would use the multiple file mappings. A table combines a head and body. So for a four column SoA (vertical) table there are 8 files (mmaps) as 4 heads and 4 bodies, with corresponding programmatic names and file names. The table abstraction similarly allows this to be defined and configured as one table, while retaining fluent names to navigate to the individual columns. These changes allow 11 tables, with 22 files to be represented as 3 tables with 6 files. And if we want to split out multisig from ecdsa and schnorr, that becomes 5 tables over 10 files, vs. 19 tables over 38 files. The actual tables and files are still there, just a lot less code overhead, thanks to the magic of metaprogramming.