3 ms·
> depending on project since it gives you absolute control Absolute control to hunt down your own bugs, instead of using something that is an industry standard
by kaba0 3y ago
> depending on project since it gives you absolute control
Absolute control to hunt down your own bugs, instead of using something that is an industry standard and any competent programmer jumping to your project can be up-to-speed with it instantly..
- isbvhodnvemrwvn 3y agoVery few developers are competent with hibernate, many fewer than with sql. Writeback cache nature of hibernate makes it very complex, order of operations on the app won't match order of operations in the DB.
- HelloNurse 3y agoEven an "industry standard" framework can get in the way. Given the constraints of executing efficient queries; handling errors and timeouts on the application's terms; and enforcing concurrency and transaction handling policies even a "good" ORM can be more a problem than a solution.
- kaba0 3y agoAll of those will be worse off by hand-made “solutions”. Especially that you are not forced to use ORM for everything. Use it for like 90% of your generic db usage, and use its in-built escape hatches for the rest, like native queries or go straight to the db driver if needed.
- JanSt 3y agoIn my experience I‘m better off not touching an ORM at all