2 ms·
Glad to see folks critique traditional ORM tropes and putting forward some innovation in the area. On that note, as a highly subjective opinion, I have really
by mmatants 11y ago
Glad to see folks critique traditional ORM tropes and putting forward some innovation in the area.
On that note, as a highly subjective opinion, I have really soured on the philosophy that guides many popular ORMs.
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 embrace the relational model, because it is actually quite apt for many business cases.
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: https://github.com/fxrm/fxrm-store-java https://github.com/fxrm/fxrm-store-java
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.
- scottysinclair 11y agoYes, I agree with you about relational data, BarleyDB holds the relational data in memory and then provides Pojo proxies to it. Combining an active record approach with a domain model Pojo approach if you like. This is why it is fully possible to use BarleyDB without compiling any classes, you can just use the in memory model instead.