AWS prescriptive-guidance documentation change
Summary
Fixed quotation mark formatting in nested loop join description
Security assessment
Change only corrects smart quotes to straight quotes without altering technical content or security context
Diff
diff --git a/prescriptive-guidance/latest/query-lifecycle-redshift/explain-joins.md b/prescriptive-guidance/latest/query-lifecycle-redshift/explain-joins.md index a2aec89d6..365636473 100644 --- a//prescriptive-guidance/latest/query-lifecycle-redshift/explain-joins.md +++ b//prescriptive-guidance/latest/query-lifecycle-redshift/explain-joins.md @@ -22 +22 @@ The following join types are commonly used in Amazon Redshift: - * **Nested loop** – A nested loop occurs when a hash table can't be created between the two tables. Nested loops are used mainly for cross-joins (Cartesian products) and some inequality joins. This will require the database to check every value in the left table against every value in the right table. The complexity of a nested loop join is “quadratic” in that you must perform approximately N*N (or N²) different operations to process the join. The nested loop is the least optimal join type. + * **Nested loop** – A nested loop occurs when a hash table can't be created between the two tables. Nested loops are used mainly for cross-joins (Cartesian products) and some inequality joins. This will require the database to check every value in the left table against every value in the right table. The complexity of a nested loop join is "quadratic" in that you must perform approximately N*N (or N²) different operations to process the join. The nested loop is the least optimal join type.