<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Incremental Computation on App Coding</title>
    <link>https://appcoding.com/tags/incremental-computation/</link>
    <description>Recent content in Incremental Computation on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/incremental-computation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Incremental View Maintenance Small Enough to Embed Turns Dashboard Queries Into Lookups</title>
      <link>https://appcoding.com/incremental-view-maintenance-small-enough-to-embed-turns-dashboard-queries-into-lookups/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/incremental-view-maintenance-small-enough-to-embed-turns-dashboard-queries-into-lookups/</guid>
      <description>&lt;p&gt;A dashboard tile shows today&amp;rsquo;s US traffic, so every page load runs &lt;code&gt;SELECT count(*) FROM events WHERE country = &#39;US&#39;&lt;/code&gt; over a table that grew by a few hundred thousand rows since yesterday. SQLite answers correctly. It also walks every matching index entry to do it, because its b-trees don&amp;rsquo;t keep counts, and it does the same walk for the next viewer and the one after. Between two page loads the answer moves by a handful of rows, yet each load pays for all of them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
