<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data History on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/data-history/</link><description>Recent content in Data History 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/data-history/index.xml" rel="self" type="application/rss+xml"/><item><title>Tracking Data Changes: Diffs, Logs, and History</title><link>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/tracking-data-changes/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-dolt-guide/tracking-data-changes/</guid><description>&lt;h2 id="introduction-the-who-what-when-of-your-data"&gt;Introduction: The &amp;ldquo;Who, What, When&amp;rdquo; of Your Data&lt;/h2&gt;
&lt;p&gt;Imagine trying to debug an issue in a traditional database. A critical value changed, but when? Who changed it? And what was it before? These questions often lead to digging through application logs, backups, or worse, shrugging your shoulders in frustration. Traditional databases often lack the built-in capabilities to answer these fundamental questions about data evolution.&lt;/p&gt;
&lt;p&gt;This is where Dolt shines. By bringing Git-style version control to your SQL database, Dolt fundamentally changes how you interact with data history. In this chapter, we&amp;rsquo;ll dive into the core Dolt commands that allow you to track, inspect, and even &amp;ldquo;time travel&amp;rdquo; through your database&amp;rsquo;s past. This knowledge is crucial for auditing, debugging, and understanding data evolution in any production environment.&lt;/p&gt;</description></item></channel></rss>