# implicit joins Published articles for implicit joins. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Hidden Benefit of Implicit Joins: Join Elimination DevFeed: [A Hidden Benefit of Implicit Joins: Join Elimination]() Original publisher: [Read original article]() Author: lukaseder Published: 2024-01-10T14:19:00Z Content type: article Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [rdbms]() Tags: [implicit-joins](), [implicit-path-join](), [java](), [join-elimination](), [jooq](), [jooq-3-19](), [jooq-in-use](), [many-to-many-joins](), [optimisation](), [path-joins](), [sql](), [to-many-joins]() ### AI overview This article explains how jOOQ 3.19 can eliminate unnecessary tables from implicit path joins when no columns from those tables are referenced. Primary and foreign keys preserve equivalence, while referenced columns cause the table to remain in the join tree. The behavior applies to implicit path joins and depends on a flag that is disabled by default. ### Source excerpt One of jOOQ's key features so far has always been to render pretty much exactly the SQL that users expect, without any surprises - unless some emulation is required to make a query work, of course. This means that while join elimination is a powerful feature of many RDBMS, it isn't part of jOOQ's feature ... Continue reading A Hidden Benefit of Implicit Joins: Join Elimination -> ## jOOQ 3.19's new Explicit and Implicit to-many path joins DevFeed: [jOOQ 3.19's new Explicit and Implicit to-many path joins]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-28T14:35:14Z Content type: release Language: en Sources: [jOOQ]() Topics: [jooq](), [jpa](), [SQL]() Tags: [correlated-subqueries](), [explicit-path-joins](), [implicit-join](), [implicit-join-path-correlation](), [implicit-joins](), [java](), [jooq](), [jooq-3-19](), [jooq-development](), [path-joins](), [sql](), [to-many-path-joins]() ### AI overview This article describes jOOQ 3.19's support for explicit path joins and new to-many path joins. It explains how path-based joins can simplify SQL queries, derive join predicates from foreign-key metadata, and allow per-query control over join types. ### Source excerpt jOOQ 3.19 finally delivers on a set of features that will greatly simplify your queries further, after jOOQ 3.11 introduced implicit to-one joins: What are these features? Many ORMs (e.g. JPA, Doctrine, jOOQ 3.11 and others) support "path joins" (they may have different names for this concept). A path join is a join derived from ... Continue reading jOOQ 3.19's new Explicit and Implicit to-many path joins -> ## 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 more DevFeed: [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 more]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-15T16:30:41Z Content type: release Language: en Sources: [jOOQ]() Topics: [releases](), [DuckDB](), [CockroachDB](), [Maven](), [Gradle](), [rdbms](), [Multi-tenancy]() Tags: [cockroachdb](), [cockroachdb-23](), [duckdb](), [gradle](), [gradle-plugin](), [implicit-joins](), [java-8](), [join-paths](), [jooq](), [jooq-3-19](), [jooq-development](), [maven](), [maven-repository](), [multi-tenancy](), [oracle-23c](), [policies](), [release-notes](), [releases](), [row-level-security](), [security](), [trigger-meta-data](), [triggers](), [trino](), [trinodb](), [udt-paths](), [udts]() ### AI overview The jOOQ 3.19.0 release adds experimental DuckDB support, Trino support, and support for CockroachDB 23 and Oracle 23c. It also improves join paths, introduces an official Gradle plugin and a commercial Maven repository, and adds policies for row-level security. ### Source excerpt New Dialects It's been a few releases since we've added support for new dialects, but finally some very interesting RDBMS of increasing popularity have joined the jOOQ family including: These dialects are available in all jOOQ editions. New dialect versions In addition to these entirely new dialects, big new CockroachDB and Oracle versions have shipped: ... Continue reading 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 more -> ## My SQL Bad Habits DevFeed: [My SQL Bad Habits]() Original publisher: [Read original article]() Author: Map Published: 2013-05-26T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [SQL](), [syntax](), [JOIN](), [ordering]() Tags: [implicit-joins](), [ordering](), [postgres](), [query](), [sql](), [syntax](), [tables]() ### AI overview The author discusses personal SQL bad habits that can make queries less clear or more error-prone. The article covers ordering or grouping by column numbers, implicit joins, insufficient comments, and manually generated lists used for filtering. ### Source excerpt I'm reasonably proficient at SQL - a coworker when pseudocoding some logic for him pointed out that my pseudocode is what he thought was executable SQL. I'm fully capable of writing clear and readable SQL - which most SQL is not. Despite that I still have several bad habits when it comes to SQL. Without further adieu heres some of my dirty laundry so hopefully others can not make the same mistakes. Order/Group by Column Numbers When quickly iterating on a query its a lot less typing to put the column number as the thing you want to order by. Here's a quick lightweight example: SELECT email, created_at FROM users ORDER BY 2 DESC LIMIT 5; This gives me my last 5 users that have signed up for my site. Of course as soon as I have this I may want to add some data to it, like their first name so I can send them a welcome email. I quickly alter the query to: SELECT email, first_name, created_at FROM users ORDER BY 2 DESC LIMIT 5; And now I have 5 users that have signed up ordered by their first name. Sure its obvious when you have 1 column you're ordering by, but when you have GROUP BY 1, 2, 3, 4, 5, 6 which is actually open in one of my tabs currently its a bit more confusing.... Though if you really want to have some fun, share a query with someone that looks something like this: SELECT email as "3", first_name "2", created_at "1" FROM users ORDER BY "1", "3" DESC LIMIT 5; Implicit Joins I seldom use the syntax INNER JOIN. Instead I simply put the two tables in my where clause and ensure I have a where condition. The problem with ensuring I have a where condition is sometimes I don't, especially when you're dealing with 3 tables. SELECT email, product.name, product.price FROM users, orders, items WHERE users.id = orders.user_id AND orders.id = items.order_id Is less clear (especially when dealing with 5-6 tables) than the alternative: SELECT email, product.name, product.price FROM users INNER JOIN orders on users.id = orders.user_id INNER JOIN items on orders.id = items.or