Glad to see folks critique traditional ORM tropes and putting forward some innovation in the area.<p>On that note, as a highly subjective opinion, I have really soured on the philosophy that guides many popular ORMs.<p>Relational data does not map to OOP well, and I think the point is not to actually force that. Instead, I think there are ways to <i>embrace</i> the relational model, because it is actually quite apt for many business cases.<p>For those further interested in the general topic of alternate ORM approaches, here is a link to a proof of concept from a while back, when I was exploring how to express column-driven data in Java code: <a href="https:&#x2F;&#x2F;github.com&#x2F;fxrm&#x2F;fxrm-store-java" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;fxrm&#x2F;fxrm-store-java</a><p>This is not to hijack attention from the OP idea, of course; just noting that this is still a fruitful area of improvement in software.