<?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: Store DateTime value 0001-01-01 in Mysql  always NULL in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Store-DateTime-value-0001-01-01-in-Mysql-always-NULL/m-p/2321693#M91702</link>
    <description>&lt;P&gt;The MySQL documentation might give you the answer you are looking for:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://dev.mysql.com/doc/refman/5.7/en/datetime.html" alt="https://dev.mysql.com/doc/refman/5.7/en/datetime.html" target="_blank"&gt;https://dev.mysql.com/doc/refman/5.7/en/datetime.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DATE... The supported range is&amp;nbsp;'1000-01-01'&amp;nbsp;to&amp;nbsp;'9999-12-31'.&lt;/P&gt;&lt;P&gt;DATETIME... The supported range is&amp;nbsp;'1000-01-01 00:00:00'&amp;nbsp;to&amp;nbsp;'9999-12-31 23:59:59'.&lt;/P&gt;&lt;P&gt;TIMESTAMP&amp;nbsp;has a range of&amp;nbsp;'1970-01-01 00:00:01'&amp;nbsp;UTC to&amp;nbsp;'2038-01-19 03:14:07'&amp;nbsp;UTC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have a MySQL install handy to test out, but my suggestion is you should try to stay within the limits of the MySQL data type.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You'll likely get differing opinions on this, but in my personal opinion there is no reason to use a default value. Especially one that would never be valid like 0001-01-01. NULLs are perfectly valid in today's DBMSs, and are handled quite gracefully in modern stacks. I have never heard a good argument for using a "dummy" default value - especially in a date or numeric field.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you don't have control over the DB schema, and you have some type of requirement to have a default value entered from Talend, please refer to the MySQL docs I linked above. There isn't much you can do if MySQL simply will not accept 0001-01-01 in a date column.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jan 2021 19:24:18 GMT</pubDate>
    <dc:creator>PaulyWally</dc:creator>
    <dc:date>2021-01-28T19:24:18Z</dc:date>
    <item>
      <title>Store DateTime value 0001-01-01 in Mysql  always NULL</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Store-DateTime-value-0001-01-01-in-Mysql-always-NULL/m-p/2321692#M91701</link>
      <description>&lt;P&gt;Hello i have an issue when i try to insert a default date value 0001-01-01 from Talend job  to my Mysql table i get a NULL value in the table .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a way to resolve this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance &lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 00:44:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Store-DateTime-value-0001-01-01-in-Mysql-always-NULL/m-p/2321692#M91701</guid>
      <dc:creator>eric012</dc:creator>
      <dc:date>2024-11-16T00:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: Store DateTime value 0001-01-01 in Mysql  always NULL</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Store-DateTime-value-0001-01-01-in-Mysql-always-NULL/m-p/2321693#M91702</link>
      <description>&lt;P&gt;The MySQL documentation might give you the answer you are looking for:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://dev.mysql.com/doc/refman/5.7/en/datetime.html" alt="https://dev.mysql.com/doc/refman/5.7/en/datetime.html" target="_blank"&gt;https://dev.mysql.com/doc/refman/5.7/en/datetime.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DATE... The supported range is&amp;nbsp;'1000-01-01'&amp;nbsp;to&amp;nbsp;'9999-12-31'.&lt;/P&gt;&lt;P&gt;DATETIME... The supported range is&amp;nbsp;'1000-01-01 00:00:00'&amp;nbsp;to&amp;nbsp;'9999-12-31 23:59:59'.&lt;/P&gt;&lt;P&gt;TIMESTAMP&amp;nbsp;has a range of&amp;nbsp;'1970-01-01 00:00:01'&amp;nbsp;UTC to&amp;nbsp;'2038-01-19 03:14:07'&amp;nbsp;UTC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have a MySQL install handy to test out, but my suggestion is you should try to stay within the limits of the MySQL data type.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You'll likely get differing opinions on this, but in my personal opinion there is no reason to use a default value. Especially one that would never be valid like 0001-01-01. NULLs are perfectly valid in today's DBMSs, and are handled quite gracefully in modern stacks. I have never heard a good argument for using a "dummy" default value - especially in a date or numeric field.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you don't have control over the DB schema, and you have some type of requirement to have a default value entered from Talend, please refer to the MySQL docs I linked above. There isn't much you can do if MySQL simply will not accept 0001-01-01 in a date column.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2021 19:24:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Store-DateTime-value-0001-01-01-in-Mysql-always-NULL/m-p/2321693#M91702</guid>
      <dc:creator>PaulyWally</dc:creator>
      <dc:date>2021-01-28T19:24:18Z</dc:date>
    </item>
  </channel>
</rss>

