<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database Versioning on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/database-versioning/</link><description>Recent content in Database Versioning on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/database-versioning/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to Dolt: Git for Your Data</title><link>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/introduction-to-dolt/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/introduction-to-dolt/</guid><description>&lt;p&gt;Imagine if your database had the superpower of Git. What if every change to your data, every schema evolution, and every critical update was tracked, diffable, branchable, and mergeable, just like your application code? This isn&amp;rsquo;t a dream—it&amp;rsquo;s Dolt.&lt;/p&gt;
&lt;p&gt;In the world of software development, Git has become an indispensable tool for managing code, collaborating with teams, and maintaining a complete history of changes. But what about data? Traditional relational databases offer some level of auditing through transaction logs or custom triggers, but they lack the native, powerful versioning capabilities that Git provides for code. This gap often leads to complex data management challenges, especially in collaborative environments or when dealing with critical data transformations.&lt;/p&gt;</description></item><item><title>Setting Up Dolt and Your First Data Commit</title><link>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/setting-up-dolt/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/setting-up-dolt/</guid><description>&lt;p&gt;Welcome to Chapter 2! In the previous chapter, we explored the &amp;ldquo;why&amp;rdquo; behind Dolt and the revolutionary concept of Git for data. Now, it&amp;rsquo;s time to roll up our sleeves and get hands-on.&lt;/p&gt;
&lt;p&gt;This chapter is your practical guide to installing Dolt, setting up your very first version-controlled SQL database, and making that crucial initial data commit. By the end, you&amp;rsquo;ll not only have Dolt running but also a foundational understanding of how to treat your data like code, ready to track every change. We&amp;rsquo;ll walk through each step, ensuring you grasp both the &amp;ldquo;how&amp;rdquo; and the &amp;ldquo;why&amp;rdquo; behind every command. This hands-on experience is critical for truly internalizing the &amp;ldquo;Git-for-Data&amp;rdquo; paradigm.&lt;/p&gt;</description></item><item><title>Evolving Your Schema: Versioned Migrations</title><link>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/schema-evolution/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/schema-evolution/</guid><description>&lt;p&gt;Databases are rarely static. As applications evolve, so too must their underlying data structures. This process of changing a database&amp;rsquo;s schema – adding columns, creating new tables, modifying constraints – is known as &lt;strong&gt;schema evolution&lt;/strong&gt;. In traditional relational databases, this can be a perilous journey, often involving complex migration scripts, downtime, and a high risk of errors.&lt;/p&gt;
&lt;p&gt;This chapter dives into how Dolt transforms schema evolution from a high-stakes operation into a controlled, versioned, and collaborative process, much like managing code changes with Git. You&amp;rsquo;ll learn the core concepts of Dolt&amp;rsquo;s Git-for-Data approach applied to schemas, how to perform versioned migrations, and how to handle schema changes with confidence.&lt;/p&gt;</description></item></channel></rss>