<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sql on philliant</title><link>https://philliant.com/tags/sql/</link><description>Recent content in Sql on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Sat, 28 Mar 2026 05:48:02 -0700</lastBuildDate><atom:link href="https://philliant.com/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>what is sql, and why it still works</title><link>https://philliant.com/posts/20260328-what-is-sql-and-why-it-still-works/</link><pubDate>Sat, 28 Mar 2026 05:48:02 -0700</pubDate><guid>https://philliant.com/posts/20260328-what-is-sql-and-why-it-still-works/</guid><description>i break down sql in plain language: what it is, how it evolved over five decades, which problems it solves best, and the core features that keep it relevant</description></item><item><title>left join an effective satellite without duplicating rows (use a cte)</title><link>https://philliant.com/posts/20260324-left-join-effective-satellite-cte/</link><pubDate>Tue, 24 Mar 2026 07:00:00 -0700</pubDate><guid>https://philliant.com/posts/20260324-left-join-effective-satellite-cte/</guid><description>when an entity link to another hub is optional, a naive left join that pulls in an effective satellite in the same from list can explode or blur grain. i isolate the current effective row in a cte and left join that instead.</description></item></channel></rss>