YogeshChauhan.com
NATURAL JOIN in Postgres
July 31, 2020

A NATURAL JOIN creates an implicit join based on the same column names in the tables.

Basically, it looks like this.

NATURAL JOIN in PostgreSQL

Natural joins can be INNER JOIN, LEFT JOIN, or RIGHT JOIN. By default it’s INNER JOIN means NATURAL JOIN = INNER JOIN by default but it will consider all the column names that are same to join the table.

Syntax:


SELECT a.column2, b.column2
FROM table a
NATURAL [INNER | LEFT | RIGHT] JOIN table b;

I am using alias as well in the syntax. You can use name of the table instead of alias. Alias makes it better to write the query. Learn more about alias in this post:

Column And Table Alias In Postgres

NATURAL [INNER] JOIN Query Example 

I am using the database for all examples. It is available on my Github public repo


SELECT c.contact_name, o.order_date 
FROM customers c NATURAL JOIN orders o;

//Output
contact_name.  order_date 
"Paul Henriot"    "1996-07-04"
"Karin Josephs"    "1996-07-05"
"Mario Pontes"    "1996-07-08"
...
...
830 rows

It’s the same result as the first example in this INNER JOIN post: INNER JOIN In Postgres

NATURAL LEFT JOIN Query Example


SELECT c.contact_name, o.order_date 
FROM customers c NATURAL LEFT JOIN orders o;

//Output
contact_name.       order_date
....
....
....
"Guillermo Fernández"    "1998-05-05"
"Jytte Petersen"    "1998-05-06"
"Michael Holz"    "1998-05-06"
"Laurence Lebihan"    "1998-05-06"
"Paula Wilson"    "1998-05-06"
"Marie Bertrand"    null
"Diego Roel"        null
...
832 rows

It’s the same result as the first example in this LEFT JOIN post: LEFT JOIN In Postgres

RIGHT LEFT JOIN Query Example


SELECT c.contact_name, o.order_date 
FROM customers c NATURAL RIGHT JOIN orders o;

//Output
contact_name.       order_date
....
....
....
"Guillermo Fern├índez"    "1998-05-05"
"Jytte Petersen"    "1998-05-06"
"Michael Holz"    "1998-05-06"
"Laurence Lebihan"    "1998-05-06"
"Paula Wilson"    "1998-05-06"
...
830 rows

It’s the same result as the first example in this RIGHT JOIN post: RIGHT JOIN In Postgres

When and why to use NATURAL JOIN?

CASE 1: In my opinion, if you have just one common (similar name) column between two or more tables and if you want to JOIN them then you should definitely go for NATURAL JOIN. 

CASE 2: If you have more than one common (similar name) columns and if you want the result to consider all the common columns, then use NATURAL JOIN.

CASE 3: Now, If you have more than one common (similar name) columns and if you want to consider specific common column then DO NOT use NATURAL JOIN.

dreamhost

Leave a Reply

Most Read

#1 How to check if radio button is checked or not using JavaScript? #2 How to set opacity or transparency using CSS? #3 Pagination in CSS with multiple examples #4 How to make HTML form interactive and using CSS? #5 Solution to “TypeError: ‘x’ is not iterable” in Angular 9 #6 How to uninstall Cocoapods from the Mac OS?

Recently Posted

Mar 3 How to embed YouTube or other video links in WordPress? Mar 3 How to change the Login Logo in WordPress? Mar 3 substring() Method in JavaScript Mar 3 Window setInterval() Method in JavaScript Mar 2 How to zoom an element on hover using CSS? Mar 2 the box-sizing property in CSS

You might also like these

Sorting Object Arrays in JavaScriptJavaScriptIf statement shorthand examples in JavaScriptJavaScriptWhere is the PHP log file located on Mac OS?PHPHow to get Current Hour, Minute and Second in JavaScript?JavaScriptKilling A Project Part 4: What Would Be Your Top 3 Priorities For Planning The Cancellation?MiscHow to Use SQL MAX() Function with Dates?SQL/MySQL