{"id":13988,"date":"2025-07-12T17:20:05","date_gmt":"2025-07-12T15:20:05","guid":{"rendered":"https:\/\/www.salvis.com\/blog\/?p=13988"},"modified":"2025-07-14T09:03:31","modified_gmt":"2025-07-14T07:03:31","slug":"outer-joining-with-ansi-sql-89-and-sql-92","status":"publish","type":"post","link":"https:\/\/www.salvis.com\/blog\/2025\/07\/12\/outer-joining-with-ansi-sql-89-and-sql-92\/","title":{"rendered":"Outer Joining With ANSI SQL-89 and SQL-92"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

I recently implemented a quick fix for the rule G-3130<\/a> to transform queries to ANSI SQL-92 syntax. One of the challenges was to handle Oracle’s outer-join syntax (+)<\/code>. In ANSI SQL-89, join and filter criteria are part of the WHERE clause. It’s not easy to distinguish them. In this blog post, I explain why it is important to do that when using outer joins, regardless of which join syntax you prefer.<\/p>\n\n\n\n

Data Setup<\/h2>\n\n\n\n

All examples in this blog post are based on the tables DEPT<\/code> and EMP<\/code>, that were originally present in every Oracle Database instance as part of the SCOTT<\/code> schema. Here’s a script to create these tables. The script requires an Oracle Database 23ai. <\/p>\n\n\n\n

1) Create table DEPT and EMP<\/span>