Merge pull request #104 from mabel-dev/FIX/#102

FIX/#102
mabel-dev · May 9, 2022 · f75b1ca · f75b1ca
2 parents 13c0ddb + 41329a5
commit f75b1ca
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/SQL Reference/08 Joins.md b/docs/SQL Reference/08 Joins.md
@@ -19,7 +19,7 @@ SELECT *
  CROSS JOIN right_table;
 ~~~
 
-<img src="../diagrams/cross-join.svg" width="400px">
+<img src="https://github.com/mabel-dev/opteryx/blob/main/docs/diagrams/cross-join.svg" width="400px">
 
 The size of the resultant dataset when using `CROSS JOIN` is length of the two datasets multiplied together (2 x 3 = 6, in the pictural example), which can easily result in extremely large datasets. When an alternate join approach is possible, it will almost always perform better than a `CROSS JOIN`.
 
@@ -41,7 +41,7 @@ SELECT *
     ON left_table.column_name = right_table.column_name;
 ~~~
 
-<img src="../diagrams/inner-join.svg" width="400px">
+<img src="https://github.com/mabel-dev/opteryx/blob/main/docs/diagrams/inner-join.svg" width="400px">
 
 ## LEFT JOIN
 
@@ -61,7 +61,7 @@ SELECT *
     ON left_table.column_name = right_table.column_name;
 ~~~
 
-<img src="../diagrams/left-join.svg" width="400px">
+<img src="https://github.com/mabel-dev/opteryx/blob/main/docs/diagrams/left-join.svg" width="400px">
 
 ## FULL JOIN
 
@@ -81,4 +81,4 @@ SELECT *
     ON left_table.column_name = right_table.column_name;
 ~~~
 
-<img src="../diagrams/full-join.svg" width="400px">
+<img src="https://github.com/mabel-dev/opteryx/blob/main/docs/diagrams/full-join.svg" width="400px">