<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why We Used Two Bronze Tables Instead of One — And Why It Mattered in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered/m-p/158030#M54649</link>
    <description>&lt;P&gt;Post removed — reposting with corrections&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jun 2026 07:05:49 GMT</pubDate>
    <dc:creator>savlahanish27</dc:creator>
    <dc:date>2026-06-01T07:05:49Z</dc:date>
    <item>
      <title>Why We Used Two Bronze Tables Instead of One — And Why It Mattered</title>
      <link>https://community.databricks.com/t5/data-engineering/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered/m-p/158030#M54649</link>
      <description>&lt;P&gt;Post removed — reposting with corrections&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2026 07:05:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered/m-p/158030#M54649</guid>
      <dc:creator>savlahanish27</dc:creator>
      <dc:date>2026-06-01T07:05:49Z</dc:date>
    </item>
  </channel>
</rss>

