TOC refresh

README.md

@@ -6,6 +6,21 @@ The following posts are in reverse chronological order: newest posts are first.
 
 | topics | date | title |
 |:-------|:-----|:------|
+| Materialize | 2023-05-19 | [Demonstrating Operational Data with SQL](https://github.com/frankmcsherry/blog/blob/master/posts/2023-05-19.md)
+| Materialize | 2023-03-18 | [Computing and Maintaining Weird (Outer) Joins](https://github.com/frankmcsherry/blog/blob/master/posts/2023-03-18.md)
+| Materialize | 2023-01-02 | [Materialize and Advent of Code (50/50)](https://github.com/frankmcsherry/blog/blob/master/posts/2023-01-02.md)
+| Materialize | 2023-12-20 | [Materialize and Memory](https://github.com/frankmcsherry/blog/blob/master/posts/2023-12-20.md)
+| Materialize | 2023-12-19 | [Doing Business with Recursive SQL](https://github.com/frankmcsherry/blog/blob/master/posts/2023-12-19.md)
+| Materialize | 2023-10-10 | [Responsiveness and Operational Agility](https://github.com/frankmcsherry/blog/blob/master/posts/2023-10-10.md)
+| Materialize | 2023-09-29 | [Freshness and Operational Autonomy](https://github.com/frankmcsherry/blog/blob/master/posts/2023-09-29.md)
+| Materialize | 2023-09-19 | [Consistency and Operational Confidence](https://github.com/frankmcsherry/blog/blob/master/posts/2023-09-19.md)
+| Materialize | 2023-09-17 | [A Guided Tour of Materialize's Product Principles](https://github.com/frankmcsherry/blog/blob/master/posts/2023-09-17.md)
+| Materialize | 2023-07-21 | [Capturing Change Data Capture (CDC) Data](https://github.com/frankmcsherry/blog/blob/master/posts/2023-07-21.md)
+| Materialize | 2023-01-04 | [Advent of Code 2022: In SQL](https://github.com/frankmcsherry/blog/blob/master/posts/2023-01-04.md)
+| Materialize | 2022-12-28 | [Reasons for Recursion](https://github.com/frankmcsherry/blog/blob/master/posts/2022-12-28.md)
+| Materialize | 2022-12-25 | [Recursion in Materialize](https://github.com/frankmcsherry/blog/blob/master/posts/2022-12-25.md)
+| Materialize | 2022-07-06 | [Minesweeping in Materialize](https://github.com/frankmcsherry/blog/blob/master/posts/2022-07-06.md)
+| Materialize | 2021-05-14 | [Maintaining Joins using Few Resources](https://github.com/frankmcsherry/blog/blob/master/posts/2021-05-14.md)
 | Differential | 2021-04-26 | [Generalizing Linear Operators](https://github.com/frankmcsherry/blog/blob/master/posts/2021-04-26.md)
 | Materialize | 2021-02-11 | [Windows enough, and Time](https://github.com/frankmcsherry/blog/blob/master/posts/2021-02-11.md)
 | Materialize | 2020-12-29 | [Slicing up Temporal Aggregates in Materialize](https://github.com/frankmcsherry/blog/blob/master/posts/2020-12-29.md)

posts/2022-07-06.md

@@ -300,6 +300,11 @@ from
     generate_series(x - 1, x + 1) as probe_x,
     generate_series(y - 1, y + 1) as probe_y;
 
+-- Each location reports some flavor of mine.
+create view reports as
+select x, y, get_byte(sha256((probe_x::text || probe_y::text)::bytes), 0) % 6 as mine, team, test
+from probes;
+
 -- The number of adjacent mines for probed locations.
 -- We include the center and subtract one to ensure we see a zero.
 create materialized view totals as
@@ -373,7 +378,7 @@ from (
             from totals
             where cells.x = totals.x
               and cells.y = totals.y
-              and cells.mine = totals.test
+              and cells.mine = totals.mine
               and cells.team = totals.team
         ),
         (   -- a `X` for mines correctly flagged by this team.
@@ -501,7 +506,7 @@ This is just a matter of looking at `totals` for counts of zero, and testing all
 -- We can test locations we know have no adjacent mines!
 -- In fact, we can do this over and over until we stop inserting things.
 create view should_test as
-select distinct new_x as x, new_y as y, test, team
+select distinct new_x as x, new_y as y, mine, team
 from
     (select * from totals where count = 0),
     generate_series(x - 1, x + 1) as new_x,
@@ -513,7 +518,7 @@ select * from distinct_tests;
 If we peek at the contents of this view, we'll see new locations that are safe to test.
 ```
 materialize=> select * from should_test where team = 'frank';
- x  | y  | test | team
+ x  | y  | mine | team
 ----+----+------+-------
   0 |  1 |    0 | frank
   0 | -1 |    0 | frank

posts/2023-09-17.md

@@ -1,3 +1,4 @@
+## A Guided Tour of Materialize's Product Principles
 
 This post is one in a series where we dive into the technical detail of Materialize's pillars of value.
 We will unpack what properties Materialize strives to do well, why they might be valuable to you, and how to see each happening (or not) in the platforms you might consider.