<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Multicte</title>
    <link>https://multicte.pages.dev/posts/</link>
    <description>Recent content in Posts on Multicte</description>
    <image>
      <title>Multicte</title>
      <url>https://tse1.mm.bing.net/th?q=multicte</url>
      <link>https://tse1.mm.bing.net/th?q=multicte</link>
    </image>
    <generator>Hugo -- 0.151.1</generator>
    <language>en</language>
    <lastBuildDate>Fri, 27 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://multicte.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Writing better SQL with a multicte approach</title>
      <link>https://multicte.pages.dev/posts/multicte/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://multicte.pages.dev/posts/multicte/</guid>
      <description>I&amp;#39;ve found that will utilizing a multicte setup within my SQL scripts really helps maintain things organized when the logic gets messy. If you&amp;#39;ve ever spent a few hours staring at the wall of nested subqueries, trying to figure out where one part</description>
    </item>
  </channel>
</rss>
