Java Champion, creator of https://jooq.org, the best way to write SQL in Java.
Will mostly tweet about Java, SQL, jOOQ, programming humour, and write at https://blog.jooq.org
Won't check Mastodon regularly, so best get in touch elsewhere!
| Java | |
| SQL | |
| jOOQ |
In case it's not clear where it works best: Whenever you need client side type safety, improved mapping, dialect agnosticity, dynamic SQL (and chances are, you'll write a lot of this, once you embrace jOOQ).
But again, jOOQ doesn't care if you're querying tables or complex views! Use those, too!
I keep seeing "hot" takes that instead of using jOOQ's DSL, people should just use native SQL.
That's just a silly false dichotomy. jOOQ *encourages* you to create views, stored procedures, plain SQL templates, etc.
Use the DSL where it works best for you *in addition* to native SQL!
New episode: "jOOQ"
Michael and Nikolay are joined by @lukaseder, the creator of jOOQ, to discuss what it is, some nice developer experience features it has, and some fun things he's come across from a Postgres perspective.
Michael and Nikolay are joined by Lukas Eder, the creator of jOOQ, to discuss what it is, some nice developer experience features it has, and some fun things he's come across from a Postgres perspe...
I think this is pretty familiar for most of us.To everyone who watches this: please check out this youtube creator called nartharie . He has created some of ...
Every time I see "bait and switch" claims related to OSS, I'm just baffled by the cynicism and glass-2%-empty pessimism, as if every supplier is just out to rip them off big time.
Why not focus on the tremendous value offered for free (even if only for a limited time), instead?
Supply chain management is important, obviously. It includes total cost of ownership considerations:
https://en.wikipedia.org/wiki/Total_cost_of_ownership
But the term "bait and switch" hints at utter cynicism. Nothing grand arises out of cynicism.
PostgresFM
Michael Simons