duckdb · szarnyasg · Oct 26, 2025 · Oct 23, 2025 · Oct 23, 2025 · Oct 23, 2025
diff --git a/_posts/2025-02-25-prefix-aliases-in-sql.md b/_posts/2025-02-25-prefix-aliases-in-sql.md
@@ -10,7 +10,7 @@ tags: ["using DuckDB"]
 
 ## Syntax
 
-<p><i>“Perhaps we <a href="https://www.youtube.com/watch?v=TBAf5l1RmcA">should just leave nature alone</a>, to its simple one-assed schematics.”</i><br/>
+<p style="text-align: right"><i>“Perhaps we <a href="https://www.youtube.com/watch?v=TBAf5l1RmcA">should just leave nature alone</a>, to its simple one-assed schematics.”</i><br/>
    — Dr. Alphonse Mephesto, South Park Episode #5</p>
 
 There is often more than one way to do things in our beloved SQL. For example, you can define join conditions *implicitly* (and dangerously) in the `WHERE` clause or use the (better) `JOIN ... ON ...` syntax. Generally, having “more than one way to do things” can be confusing and even outright [dangerous sometimes](https://www.youtube.com/watch?v=noQcWra6sbU).

diff --git a/_posts/2025-10-27-movies-in-databases.md b/_posts/2025-10-27-movies-in-databases.md
diff --git a/images/blog/movies/average_frame_68.png b/images/blog/movies/average_frame_68.png
diff --git a/images/blog/movies/charade-poster.jpg b/images/blog/movies/charade-poster.jpg
diff --git a/images/blog/movies/frame.png b/images/blog/movies/frame.png
diff --git a/images/blog/movies/table.html b/images/blog/movies/table.html
diff --git a/images/blog/thumbs/movies-in-databases.png b/images/blog/thumbs/movies-in-databases.png
diff --git a/images/blog/thumbs/movies-in-databases.svg b/images/blog/thumbs/movies-in-databases.svg