3 ms·
I agree. Hibernate has become a downright liability at times in our codebase. These days I only use it in new code for query parameterization and result row tra
by EdwardDiego 13y ago
I agree. Hibernate has become a downright liability at times in our codebase. These days I only use it in new code for query parameterization and result row transforms into models.
Speaking of which, if anyone knows of a good library for query parameterization alone, let me know...
- ZitchDog 13y agoJDBI is quite good: http://jdbi.org/ http://jdbi.org/
- EdwardDiego 13y agoCheers mate! That createQuery() call looks to be exactly what I need (query safety on a low level JDBC stream object).
- allengeorge 13y agoA second shoutout for JDBI. I don't attempt to use it for anything fancy, but it hides a lot of the JDBI boilerplate in a very sane way.
- umut 13y agoWe use JDBI @Truecaller together with Metrics library. Not only it is clean and tidy, it also gives you immediate profiling around your database calls. This is priceless in a big service oriented environment. With it, you can exactly see the rate of happening (mean/last 1/5/15 minutes average) and latency (mean/avg/std-dev/75/95/98/99/99,9percentiles) for each database query. I wouldn't want to go back to manual logging and optimization hell. JDBI+Metrics opens a totally new dimension to your monitoring/profiling/optimization!
- mushishi 13y agoCheckout Dalesbred, http://dalesbred.evident.fi/ http://dalesbred.evident.fi/ It's our in-house jdbc library, and has IDEA plugin. We use it in many small projects, and in one major.
- penrod 13y agoThis might be of interest to you: https://github.com/gilesjb/copalis.sql https://github.com/gilesjb/copalis.sql