Due to the Liquibase license change to the FSL, I've deprecated the LiquibaseDatabase, which is used for jOOQ code generation: github.com/jOOQ/jOOQ/is... Going forward, the recommended way to integrate Liquibase with jOOQ is by using testcontainers: blog.jooq.org/using-testco...

Some RDBMS have a weird understanding of case sensitivity in identifiers. Here's Google Spanner. - Quoting doesn't affect case sensitivity - DDL identifiers are case sensitive (though "duplicates" are not allowed) - DML identifiers are not case sensitive

gvenzl/oracle-free images are now available for #Oracle AI #Database 23.26.0!

This is... something: aws.amazon.com/de/blogs/big...

What do you folks think? Is this a good email footer? “The bureaucracy is expanding to meet the needs of the expanding bureaucracy.” ― Oscar Wilde

What on earth is AWS Clean Rooms SQL?? docs.aws.amazon.com/clean-rooms/...

Recursive generics are so tricky to grasp because they rely on grasping recursive generics.

Did we as an industry just collectively agree that "bouncy castle" is a very secure sounding term for a "security provider," yes? downloads.bouncycastle.org/java/docs/bc...

So, we now have: - BigQuery - ClickHouse - Databricks - DuckDB - Exasol - H2 - Snowflake - Teradata (the inventor, I think?) And now also: - Oracle! I'm assuming MySQL will follow suit, soon? PostgreSQL, when!?

Apply the Oct 2025 Release Update and Oracle Database 23ai becomes Oracle AI Database 26ai This adds the QUALIFY clause QUALIFY filters window functions after grouping Like the HAVING clause does for aggregate functions SELECT ... FROM ... QUALIFY fn OVER ( ... ) > ...

Well, that's something! The Derby Database is unsupported ("retired"). It has been around forever, I'm kinda feeling nostalgic about this... issues.apache.org/jira/browse/...

Q: Does your RDBMS use zero-based or one-based indexing? A: Yes

Are you making any of these common #SQL mistakes? Forgetting about NULL Processing data in Java memory Using JDBC Pagination to paginate large results Using aggregate instead of window functions @lukaseder.bsky.social explains what to do instead & lists 7 more

Thanks to a sponsor, the upcoming jOOQ 3.21 will have support for the Google Spanner dialect! github.com/jOOQ/jOOQ/is...

This always struck me as one of the biggest cognitive dissonances in programming style guides

Found an actual German word de.wikipedia.org/wiki/Lieferk...

Writing a CREATE TABLE statement in SQL be like

Whaat, a Java record component cannot be deprecated by Javadoc, only by annotation? That looks like a bug in javac to me, no? The JLS doesn't mention Javadoc explicitly: docs.oracle.com/javase/specs...

Back to SQL: How jOOQ puts you in the driver's seat with @martinelli.ch www.youtube.com/watch?v=QZ8S...

Every time I write new integration test for a jOOQ bug, I also write an integration test for an RDBMS bug

Every. Time. Why. Does. It. Complain. 😬 Oooh, that's why. 😅

This sounds like my recent experience with OSGi tutorials

"5 HoUrS oF TrIaL AnD ErRoR SaVeS YoU 10 MiNuTeS oF ReAdInG ThE DoCuMeNtAtIoN." The documentation:

Debugging jOOQ bugs be like

PostgreSQL. Why do you betray me? Where are my nulls??

SQL can be so subtle, at times

I mean, jOOQ isn't like that but many are, I think?

It's so hard to be opinionated in programming

Another cool improvement of jOOQ 3.21: Implement a custom Formatter to tell jOOQ how to embed your user defined type (e.g. hstore, etc.) in a SQL/JSON or SQL/XML document in order to serialise it with MULTISET queries: github.com/jOOQ/jOOQ/is...

How to fetch multiple to-many relationships with jOOQ MULTISET vladmihalcea.com/fetch-multip...

My inbox before and after the CI/CD server noticed the short github outage.

Coming to jOOQ 3.21, emulation of named parameters in stored function calls, when the underlying RDBMS doesn't support named parameters, but supports defaulted params, such as Firebird: github.com/jOOQ/jOOQ/is...

Is it really happening today??? 🥹

Hmm, I wish the JDK had a few additional methods in Collections, similar to synchronizedMap(), but with a ReadWriteLock instead of a mutex. Two read operations shouldn't block each other.

See you at the JUGS summer party! www.jug.ch/html/events/...

Apparently, the generated hashCode() implementation of Java 16 records is significantly slower in benchmarks than what could be hand-written, or e.g. Eclipse generated, probably due to additional stack frames and varargs allocation in Objects::hash Details: github.com/jOOQ/jOOQ/is...

Fun fact, -9223372036854775808L is not a valid literal in the Kotlin language (because the - sign isn't part of the literal, it seems)

Join me on the .NET community standup in a bit! www.youtube.com/watch?v=EbFq...

Remember kids, while bind values in SQL are almost always a good thing by default, sometimes, inlining a constant value into the query is better for performance. See this article: blog.jooq.org/when-to-use-...

PostgreSQL tables without columns are an interesting thing. There are other ways to construct them, but this approach strikes me as particularly funny.

The rows returned by the core #SQL joins are INNER Rows with matching values for the join column in both tables OUTER All the rows from the outer table with matching rows from the inner table. A FULL OUTER JOIN preserves both tables CROSS Every row combined with every other

Id like a reality check here, am I the tyrant for requesting manual reviews of generated code from tools like jOOQ or QueryDSL? Do people just put these generators blindly into their pipelines, either gen on build or build & merge into main?

Did you know PostgreSQL has built-in enum types? I use them in all my business applications with jOOQ. jOOQ automatically creates a matching Java enum, so you get compile-time checks and IDE support. www.postgresql.org/docs/current...

GROUP BY ALL as understood by Databricks, DuckDB, Oracle, Snowflake (and others?) seems useful, but ugh would it have hurt to consider ISO/IEC 9075 first? The standard already specifies GROUP BY [ ALL | DISTINCT ], with an entirely different semantics (as correctly observed by PostgreSQL)

I've always thought it was obvious that [[1,2],[3,4]] is a more efficient JSON data format than [{"a":1,"b":2},{"a":3,"b":4}], if you can handle the reduced readability, such as in jOOQ's MULTISET via SQL/JSON emulation: blog.jooq.org/consider-usi...

Me, when working with generics

Could be worse

How has no one told me yet what a culinary gem Stockholm is???

Huh, this is a neat one. MySQL has had it for ages, and I've always wondered why no one would copy it, given that it's just like UPDATE, it's much more readable, and 95% of all INSERT statements are single row inserts anyway.

Oracle Database 23.9 is out, once again, this RU has several #SQL features you're sure to enjoy Here's a summary of a few