<?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 Re: Data Warehouse in Databricks Date values as date or int: what is recommended? in Warehousing &amp; Analytics</title>
    <link>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/67166#M1288</link>
    <description>&lt;P&gt;Definitely +1.&lt;BR /&gt;You don't want to lose leading zeroes f.e.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Apr 2024 07:49:20 GMT</pubDate>
    <dc:creator>-werners-</dc:creator>
    <dc:date>2024-04-24T07:49:20Z</dc:date>
    <item>
      <title>Data Warehouse in Databricks Date values as date or int: what is recommended?</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/66062#M1275</link>
      <description>&lt;P&gt;In&amp;nbsp; relational data warehouse systems it was best practise to represent date values as YYYYMMDD integer type values in tables. Date comparison could be done easily without using date-functions and with low performance impact.&lt;/P&gt;&lt;P&gt;Is this still the recommended way in a delta lakehouse architecture?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 09:29:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/66062#M1275</guid>
      <dc:creator>DataFarmer</dc:creator>
      <dc:date>2024-04-11T09:29:50Z</dc:date>
    </item>
    <item>
      <title>Re: Data Warehouse in Databricks Date values as date or int: what is recommended?</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/67055#M1284</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/100878"&gt;@DataFarmer&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I Databricks I will advise you to use &lt;STRONG&gt;date&lt;/STRONG&gt; type instead of int, this will make your life much simpler while working on the date type data.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 12:39:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/67055#M1284</guid>
      <dc:creator>Ajay-Pandey</dc:creator>
      <dc:date>2024-04-23T12:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: Data Warehouse in Databricks Date values as date or int: what is recommended?</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/67166#M1288</link>
      <description>&lt;P&gt;Definitely +1.&lt;BR /&gt;You don't want to lose leading zeroes f.e.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2024 07:49:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/data-warehouse-in-databricks-date-values-as-date-or-int-what-is/m-p/67166#M1288</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2024-04-24T07:49:20Z</dc:date>
    </item>
  </channel>
</rss>

