Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

jooq

Filed under this by 33 pieces from 1 source · the whole ledger

  1. Simplifying ANTI JOIN with jOOQ Syntaxjooq.orgstory
  2. Managing Sensitive Data in jOOQ 3.21+ Logsjooq.orgstory
  3. Resisting the Urge to Document Everything Everywherejooq.orgstory
  4. jOOQ 3.20 released with ClickHouse, Databricks, and much more DuckDB support, new modules, Oracle type hierarchies, more spatial support, decfloat and synonym support, hidden columns, Scala 3, Kotlin 2, and much morejooq.orgstory
  5. A Hidden Benefit of Implicit Joins: Join Eliminationjooq.orgstory
  6. jOOQ 3.19’s new Explicit and Implicit to-many path joinsjooq.orgstory
  7. jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much morejooq.orgstory
  8. To DAO or not to DAOjooq.orgstory
  9. How to Generate Package Private Code with jOOQ’s Code Generatorjooq.orgstory
  10. How to Pass a Table Valued Parameter to a T-SQL Function with jOOQjooq.orgstory
  11. How to use jOOQ’s Converters with UNION Operationsjooq.orgstory
  12. How to Write a Derived Table in jOOQjooq.orgstory
  13. Why You Should Execute jOOQ Queries With jOOQjooq.orgstory
  14. jOOQ’s R2DBC LoggingConnection to log all SQL statementsjooq.orgstory
  15. When to Use jOOQ and When to Use Native SQLjooq.orgstory
  16. Calling Procedures with Default Parameters using JDBC or jOOQjooq.orgstory
  17. Using jOOQ’s Implicit Join From Within the JOIN .. ON Clausejooq.orgstory
  18. A Brief Overview over the Most Common jOOQ Typesjooq.orgstory
  19. The Second Best Way to Fetch a Spring Data JPA DTO Projectionjooq.orgstory
  20. Cannot resolve symbol ‘VERSION_3_17’ in jOOQ generated codejooq.orgstory
  21. jOOQ 3.17 Supports Implicit Join also in DMLjooq.orgstory
  22. A Condition is a Fieldjooq.orgstory
  23. The Many Ways to Return Data From SQL DMLjooq.orgstory
  24. How to Integration Test Stored Procedures with jOOQjooq.orgstory
  25. Using H2 as a Test Database Product with jOOQjooq.orgstory
  26. The Best Way to Call Stored Procedures from Java: With jOOQjooq.orgstory
  27. Create Dynamic Views with jOOQ 3.17’s new Virtual Client Side Computed Columnsjooq.orgstory
  28. 3.17.0 Release with Computed Columns, Audit Columns, Pattern Matching, Reactive Transactions and Kotlin Coroutine Supportjooq.orgstory
  29. How to Filter a SQL Nested Collection by a Valuejooq.orgstory
  30. The Performance of Various To-Many Nesting Algorithmsjooq.orgstory
  31. Changing SELECT .. FROM Into FROM .. SELECT Does Not “Fix” SQLjooq.orgstory
  32. The Many Different Ways to Fetch Data in jOOQjooq.orgstory
  33. How to Typesafely Map a Nested SQL Collection into a Nested Java Map with jOOQjooq.orgstory

A topic here is a label each publisher printed on its own piece. Equal labels from different publishers are shown together; that does not make them one subject.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Where this comes from

Solid branches are exact SourceFrontier census edges used by this page. Folded branches share the publisher but did not supply these items.

Hacker News

1 feed · 1 available · hn.algolia.com

text1 channel · 1 available
  1. Used here by hn-new hacker-attention Hacker News
    used on this pagehacker-attention

Latest

High performance policy routed IPsec mesh SD-WANlobste.rs High performance policy routed IPsec mesh SD-WANysun lobste.rs A New Way to Think About Borrow Checking (In Reverse)lobste.rs A New Way to Think About Borrow Checking (In Reverse)Verdagon lobste.rs ARP! Tell your network to explain itselflobste.rs ARP! Tell your network to explain itselfbenj lobste.rs Algorithmic Sound Design with L-Systems and Granular Synthesischrisl lobste.rs It's enough - vibecoding tag crossed from useless to harmfulThe vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of. Please split it or kill it. But we'd be better off without what exists today. Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting arviraptor lobste.rs Un-hanging the HP Envy 17-DA0013dx for OpenBSDzk lobste.rs Making Hybrid Images (2014)zk lobste.rs