Tessera
Folgen

Lukas Eder

@lukaseder.bsky.social

Java Champion, creator of jOOQ, the best way to write SQL in Java. Will mostly post about Java, SQL, jOOQ, programming humour, and write at https://blog.jooq.org

602 Posts1135 Follower35 Folgt
Lukas Eder@lukaseder.bsky.social · 5d ago

I have no idea how to make Eclipse plugins. I just made one using Claude, to syntax highlight and type check jOOQ's internal preprocessor tag syntax. It was a single prompt and it already works! This is otherworldly 🤯

Bild
Lukas Eder@lukaseder.bsky.social · last wk.

Some weeks ago, a "harmless" DuckDB upgrade required a Ubuntu upgrade, which broke Testcontainers, Docker, and SQL Server on Ubuntu. I'm now upgrading 50 other things. We as an "engineering" field really suck at backwards compatibility, don't we?

Lukas Eder@lukaseder.bsky.social · 2w ago

I keep seeing people online who think that they have to write *all* SQL using the jOOQ DSL, once they're using jOOQ. This couldn't be further from the truth. Views are a wonderful tool in all SQL databases, allowing to create libraries of common SQL queries.

Lukas Eder@lukaseder.bsky.social · last mo.

@sivalabs.in Hey there, I found your tweet here: x.com/sivalabs/sta... Can't reply there anymore, because I don't have an account. But what was the issue with the jOOQ Gradle plugin?

Siva (@sivalabs) on X

Started adding support jOOQ and got it done with Maven quickly. Then started exploring how to integrate with Gradle that should work with different databases and Flyway/Liquibase using Testcontainers. Then I went into rabbit hole of exploring various plugins and none of them

x.com

SQLDaily@sqldaily.bsky.social · 3mo ago

You can join tables with common column names with t1 JOIN t2 USING ( col ) But this leads to a trap! With t1 JOIN t2 USING ( c1 ) JOIN t3 USING ( c2 ) With c2 in just t2 and t3 this works But add c2 to t1 in the future it breaks 😖 @lukaseder.bsky.social demos

Avoiding SQL Ambiguities caused by JOIN USING and NATURAL JOIN

Discover the pitfalls of using SQL's NATURAL JOIN and JOIN USING syntax. Learn best practices for joining tables in production queries.

buff.ly

Lukas Eder@lukaseder.bsky.social · 4mo ago

It's funny how some customers explicitly forbid using their logos on the jOOQ website, only for their engineers to tell just about anyone that they're using jOOQ at every occasion as well as talk to me about it in public 😅

SQLDaily@sqldaily.bsky.social · 4mo ago

There are joins that can only return rows from the left table Semi join => rows matching the right (IN or EXISTS) Anti join => rows not matching the right (NOT IN or NOT EXISTS) @lukaseder.bsky.social makes the case these should have their own #SQL syntax

Semi Join and Anti Join Should Have Their Own Syntax in SQL

Relational algebra nicely describes the various operations that we know in SQL as well from a more abstract, formal perspective. One of the most common relational JOIN operations is the “equi…

buff.ly

Lukas Eder@lukaseder.bsky.social · 4mo ago

Good news for PostgreSQL / pgjdbc users! There's work on binary UDT serialisation support via JDBC's SQLData API: github.com/pgjdbc/pgjdb... I'm adding experimental support for it in jOOQ: github.com/jOOQ/jOOQ/is... This should speed up UDT support quite a bit!

feat: type cache rework, codec API, and composite-type round-trip by vlsi · Pull Request #3062 · pgjdbc/pgjdbc

The original goal was to fix TypeInfoCache: many Maps for navigating between oids, names, and other information — hard to maintain, hard to invalidate no support for identifier quoting or search_p...

github.com

Lukas Eder@lukaseder.bsky.social · 6mo ago

After 18 years of maknig jOOQ, I'm still discovering such subtle differences where trying to insert a long string into a VARCHAR(n) column will raise an error if too long, but casting it to VARCHAR(n) will silently truncate it, e.g. in PostgreSQL: github.com/jOOQ/jOOQ/is... SQL is full of surprises

Bind variable casts truncate VARCHAR(n) ARRAY contents instead of letting the target INSERT raise an error · Issue #19814 · jOOQ/jOOQ

A recently added integration test creates this table: create table "t" ( "dummy" int, "s0" varchar[], "s3" varchar(3)[], primary key ("dummy") ) And asserts that if inserting array['abcd'] into s3,...

github.com

Lukas Eder@lukaseder.bsky.social · 7mo ago

Man, I just love my job. Interesting problems, happy customers, the joys of a great product market fit, flexible work hours (and not too many anymore). Thanks to all you jOOQ customers out there, making this dream-come-true possible!

Lukas Eder@lukaseder.bsky.social · 7mo ago

Huh, interesting. It appears that PostgreSQL decided to go against the SQL standard here ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor> GR 4) b) i) says that empty tables should produce a JSON array with no elements (intuitively), not NULL. Why this behaviour in PG?

Bild