Add JOINs piece to relational databases section #470
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 16.5%, saving 143.38 KB.
237 images did not require optimisation. |
|
|
||
| ## Introduction | ||
|
|
||
|  |
There was a problem hiding this comment.
remove the header image from the page. In Data Guide, we only use it as meta image.
There was a problem hiding this comment.
Personally think it'll be a good addition! I noticed these pages have a header image: Database migrations and Expand and Contract.
But if we really want to remove, I totally can 🙂
There was a problem hiding this comment.
great article, Grishma! really nice explanations and visuals of the different JOIN types. I've left a couple of comments/suggestions that I think would make the article even nicer to read and better to understand in some areas. overall fantastic work though 👏
| To address this duplication, we can pair `LATERAL JOIN`s with JSON aggregation. JSON aggregation helps avoid duplication by consolidating multiple related records into a single field as a JSON array, while `LATERAL JOIN`s help improve readability and can optimize performance. | ||
|
|
||
| Here is an example of what the result set would look like using `LATERAL JOIN`s with JSON aggregation: | ||
|
|
There was a problem hiding this comment.
would be nice to see the query that led to this result set!
There was a problem hiding this comment.
great article, Grishma! really nice explanations and visuals of the different JOIN types. I've left a couple of comments/suggestions that I think would make the article even nicer to read and better to understand in some areas. overall fantastic work though 👏
Co-authored-by: Nikolas <[email protected]>
|
Hi @nikolasburk, I implemented the changes last Friday EOD - let me know if you think it's ready to merge. Thanks! |
No description provided.