<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DBSP: Automatic Incremental View Maintenance for Rich Query Languages · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2203.16684/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2203.16684/feed.xml" rel="self" type="application/rss+xml" /><item><title>DBSP: Automatic Incremental View Maintenance for Rich Query Languages — mentioned by giovannibonetti</title><link>https://news.ycombinator.com/item?id=50127528</link><guid isPermaLink="false">urn:hackerpapers:mention:2203.16684:50127528</guid><pubDate>Sat, 17 Oct 2026 03:10:06 GMT</pubDate><description>&lt;p&gt;&amp;gt; Real progress happens by expanding the area of the envelope, not by coloring in the blanks. Respectfully disagree. What one person may classify as expanding the envelope, another one with broader knowledge may classify as coloring in the blanks. Much knowledge in one field comes from cross-pollination from other fields. Let me give you an example I just learned about. The database community spent decades trying (to some extent) to solve the implementation of materialized views to arbitrary complex SQL queries. Then, a few years ago, someone with experience in digital signal processing…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2203.16684/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item><item><title>DBSP: Automatic Incremental View Maintenance for Rich Query Languages — mentioned by cube2222</title><link>https://news.ycombinator.com/item?id=41686227</link><guid isPermaLink="false">urn:hackerpapers:mention:2203.16684:41686227</guid><pubDate>Sun, 29 Sep 2024 10:02:07 GMT</pubDate><description>&lt;p&gt;This looks extremely cool. This is basically incremental view maintenance in databases, a problem that almost everybody (I think) has when using SQL databases and wanting to do some derived views for more performant access patterns. Importantly, they seem to support a wide breath of SQL operators, support spilling computation state to disk, and it&amp;#x27;s open-source! Interestingly, it compiles queries to Rust, so an approach similar to Redshift (which compiles queries to C++ programs). There&amp;#x27;s already a bunch of tools in this area: 1. Materialize[0], which afaik is more big-data oriented, and…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2203.16684/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
