<?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 RollupDB.com</title>
    <link>https://rollupdb.com/tags/sql/</link>
    <description>Recent content in Sql on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/sql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RollupDB Adds SQL, Automatic Rollups and Streams That Can Change</title>
      <link>https://rollupdb.com/rollupdb-adds-sql-automatic-rollups-and-streams-that-can-change/</link>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/rollupdb-adds-sql-automatic-rollups-and-streams-that-can-change/</guid>
      <description>&lt;p&gt;RollupDB 0.4.0 is out. Since the first release three things have been added, one per version: rollups that run on their own, stream definitions you can change after the fact, and a read-only SQL interface over the retained buckets. Each one came out of the same question: what does someone need on day thirty that they didn&amp;rsquo;t need on day one?&lt;/p&gt;&#xA;&lt;p&gt;The short answer is that people forget to run &lt;code&gt;advance&lt;/code&gt;, they find out their retention was wrong, and they want to ask questions the JSON query wasn&amp;rsquo;t shaped for. So now &lt;code&gt;rollupdb serve&lt;/code&gt; rolls up every stream once a minute, a stream can take a new version with different retention or an added sketch, and every stream is a SQL view.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
