<?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: Why is a date datatype replicated as datetime in MySQL target endpoint in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411444#M9094</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/2924"&gt;@desmondchew&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;There are several options to control the behavior. The easiest way is using a Global Transformation to convert datetime to date, as:&lt;/P&gt;
&lt;PRE class="H100W100 preProductWizardSummary ng-binding"&gt;Convert data type
	for %.% with column % and data type DATETIME
	to data type DATE&lt;/PRE&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="john_wang_0-1706277853198.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/158453iE2E079CF11E63D12/image-size/medium?v=v2&amp;amp;px=400" role="button" title="john_wang_0-1706277853198.png" alt="john_wang_0-1706277853198.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jan 2024 14:04:43 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2024-01-26T14:04:43Z</dc:date>
    <item>
      <title>Why is a date datatype replicated as datetime in MySQL target endpoint</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411429#M9093</link>
      <description>&lt;P&gt;We are replicating tables from Oracle 11g into MySQL 8.0. We found that tables with "date" datatype columns in Oracle are replicated as "datetime" in MySQL target endpoint.&lt;/P&gt;
&lt;P&gt;According to the documentation here--&amp;gt; &lt;A href="https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/MySQL/mysql_db_target_data_types.htm#ar_mysql_902766750_1421922" target="_blank"&gt;https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/MySQL/mysql_db_target_data_types.htm#ar_mysql_902766750_1421922&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;It says that the date datatype should replicate as date. But it become datetime as default under the transformation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2024 13:47:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411429#M9093</guid>
      <dc:creator>desmondchew</dc:creator>
      <dc:date>2024-01-26T13:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: Why is a date datatype replicated as datetime in MySQL target endpoint</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411444#M9094</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/2924"&gt;@desmondchew&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;There are several options to control the behavior. The easiest way is using a Global Transformation to convert datetime to date, as:&lt;/P&gt;
&lt;PRE class="H100W100 preProductWizardSummary ng-binding"&gt;Convert data type
	for %.% with column % and data type DATETIME
	to data type DATE&lt;/PRE&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="john_wang_0-1706277853198.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/158453iE2E079CF11E63D12/image-size/medium?v=v2&amp;amp;px=400" role="button" title="john_wang_0-1706277853198.png" alt="john_wang_0-1706277853198.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2024 14:04:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411444#M9094</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2024-01-26T14:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: Why is a date datatype replicated as datetime in MySQL target endpoint</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411789#M9124</link>
      <description>&lt;P&gt;Hi John,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thank you I will try on the solution give. What I am actually asking is why is the datatype date replicate as "datetime" in MySQL when the document says it should be "date"?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 07:42:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411789#M9124</guid>
      <dc:creator>desmondchew</dc:creator>
      <dc:date>2024-01-29T07:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why is a date datatype replicated as datetime in MySQL target endpoint</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411890#M9134</link>
      <description>&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Hello team,&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Regards,&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Sushil Kumar&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 10:38:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411890#M9134</guid>
      <dc:creator>SushilKumar</dc:creator>
      <dc:date>2024-01-29T10:38:01Z</dc:date>
    </item>
    <item>
      <title>Re: Why is a date datatype replicated as datetime in MySQL target endpoint</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411963#M9140</link>
      <description>&lt;P&gt;Hello Desmond &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/2924"&gt;@desmondchew&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Good question.&lt;BR /&gt;This is how Replicate designed to make sure the DATE in Oracle can be hold completely in MySQL.&lt;/P&gt;
&lt;P&gt;DATE in Oracle is stored in 7 bytes, the first 4 bytes presents date, the last 3 bytes presents time. Although the default format of DATE in Oracle shows as DD-MON-YY but it actually have time part. The DATE presents pretty long period, eg from BC 4712.01.01.&lt;/P&gt;
&lt;P&gt;DATE in MySQL is stored in 3 bytes. And there are DATE and DATETIME datatypes in MySQL. From storage size, The match datatype DATE in Oracle should be map to DATETIME in MySQL, otherwise some values overflows in MySQL. So that depends on the precision you want. If you prefer the precision to date, then DATE type in MySQL is good enough. If you want precision set to seconds, then DATETIME type is needed in MySQL.&lt;/P&gt;
&lt;P&gt;thanks,&lt;BR /&gt;John.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 12:39:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Why-is-a-date-datatype-replicated-as-datetime-in-MySQL-target/m-p/2411963#M9140</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2024-01-29T12:39:40Z</dc:date>
    </item>
  </channel>
</rss>

