Waiting for SQL:202y: Stockholm (BMA) meeting report
- From: Saqib Ali | Date: Thu, 02 Jul 2026 01:36:58 +0000 #
Subject: Waiting for SQL:202y: Stockholm (BMA) meeting reporthttps://peter.eisentraut.org/blog/2026/06/30/waiting-for-sql-202y-stockholm-meeting-report The most recent meeting of ISO/IEC JTC1 SC32 WG3 "Database Languages" took place from the 15th to the 19th of June 2026 in Stockholm. "WG3", as we call it, works on standardizing the database languages SQL and GQL. In that meeting, a number of proposals that are of interest to SQL and PostgreSQL were accepted, which I want to report about here. The meeting code of this meeting was "BMA", which is the code for a small airport in Stockholm. All in-person WG3 meetings are named after a nearby airport. In this case, the code "ARN" for Stockholm's main airport had already been used for a meeting in 2003. Read More: https://peter.eisentraut.org/blog/2026/06/30/waiting-for-sql-202y-stockholm-meeting-report- |-- Reply
- |-- ReplyFrom: Veronika Franklin | Date: Fri, 10 Jul 2026 01:58:05 +0000 #A nice blogpost by Dani Schnider on the new addition to Standard SQL- JOIN TO ONE syntax in Standard SQL: https://danischnider.wordpress.com/2026/06/30/join-to-one-and-constraints/ The article introduces Oracle's new JOIN TO ONE syntax, which is designed to simplify "row-widening only queries" (RWOQs) by safely joining tables without risking duplicate rows. It explains how this feature helps avoid the need for workarounds like DISTINCT or subqueries when you only want to add columns from a related table, provided there's a unique or primary key constraint enforcing the one-to-one or many-to-one relationship. The post also discusses the importance of such constraints for the optimizer to correctly validate and use JOIN TO ONE without producing incorrect results.
Keyboard Shortcuts:
[ j/n next | k/p prev | g top | r reply | u up ]