News for hackers. Stuff that matters.

A comment on SQL is 43 years old – Here’s why we still use it today. Parent comment

Re:SQL is 43 years old – Here’s why we still use it today by matwood on Tuesday May 02, 2017 @01:18PM (#14248348)
> Do you hand-roll your own caching mechanism when just writing plain SQL?

Using something like jOOQ has meant I rarely need any caching, unlike Hibernate where caching almost seems required.

[ Parent | on HN ]
Re:SQL is 43 years old – Here’s why we still use it today by mindcrime on Tuesday May 02, 2017 @01:22PM (#14248399)
Interesting. I've never used jOOQ, but I'll give it a look. Hibernate has worked well for me, but I'm not dogmatic about it. Always interested to try new tools.
[ Parent | on HN ]
Re:SQL is 43 years old – Here’s why we still use it today by matwood on Tuesday May 02, 2017 @01:39PM (#14248600)
I've been writing SQL for almost 20 years, so the pain for me is the grunt mapping of data to and from. jOOQ does much of the grunt work of mapping, and lets me write typed SQL that it smartly translates to queries. More advanced features like various types of fetch make my job even easier.

https://www.jooq.org/doc/3.9/manual-single-page/#arrays-maps...

[ Parent | on HN ]