<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Grain on philliant</title><link>https://philliant.com/tags/grain/</link><description>Recent content in Grain on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Tue, 24 Mar 2026 07:00:00 -0700</lastBuildDate><atom:link href="https://philliant.com/tags/grain/index.xml" rel="self" type="application/rss+xml"/><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>