<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Audit Trails on App Coding</title>
    <link>https://appcoding.com/tags/audit-trails/</link>
    <description>Recent content in Audit Trails on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/audit-trails/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Store Changes Instead of Current Rows: An Embedded Database Built Around History</title>
      <link>https://appcoding.com/store-changes-instead-of-current-rows-an-embedded-database-built-around-history/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/store-changes-instead-of-current-rows-an-embedded-database-built-around-history/</guid>
      <description>&lt;p&gt;A support ticket asks two plain questions: which plan was customer 4411 on when the August invoice went out, and who moved them off it? The &lt;code&gt;customers&lt;/code&gt; table can&amp;rsquo;t answer either. It holds today&amp;rsquo;s row. The audit table someone added two years ago holds most of the story, apart from the week a data fix ran a bulk &lt;code&gt;UPDATE&lt;/code&gt; in raw SQL and skipped the ORM callbacks that write the audit rows.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
