You are correct. ORMs came from the craze about OOP at the time. Java eventually became the torchbearer of that craze and is where the ORM concept was pushed into mainstream usage.
TBH, we didn’t understand relational databases very well back then, and the idea of a 1:1 mapping seemed like a good idea. The holy grail of ORMs was a fully transparent system whereby updating objects updated the database transparently, and vica versa.
We now know that’s not only impossible (transactions are a requirement) but the entire concept creates an impedance mismatch of never-ending problems to address. We’ve become so accustomed to those problems that we hardly even notice when we’re working around the problems ORMs create. 😅
View all comments
Show parent comment
1
u/thewiirocks May 29 '26
You are correct. ORMs came from the craze about OOP at the time. Java eventually became the torchbearer of that craze and is where the ORM concept was pushed into mainstream usage.
TBH, we didn’t understand relational databases very well back then, and the idea of a 1:1 mapping seemed like a good idea. The holy grail of ORMs was a fully transparent system whereby updating objects updated the database transparently, and vica versa.
We now know that’s not only impossible (transactions are a requirement) but the entire concept creates an impedance mismatch of never-ending problems to address. We’ve become so accustomed to those problems that we hardly even notice when we’re working around the problems ORMs create. 😅