<?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: tMySqlOutput use case in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371546#M134468</link>
    <description>&lt;P&gt;it is not a Talend issue, this is relate to MySQL and it's support of UTF (and error text - not from Talend, but from MySQL)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so, the proper place for search the answer - database related forums&lt;/P&gt;
&lt;P&gt;as, example -&amp;nbsp;&lt;A href="https://stackoverflow.com/questions/6466901/mysql-distinction-between-e-and-é-e-acute-unique-index" target="_self" rel="nofollow noopener noreferrer"&gt;https://stackoverflow.com/questions/6466901/mysql-distinction-between-e-and-é-e-acute-unique-index&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VARCHAR is always not best idea as Primary Key, but&amp;nbsp;&lt;/P&gt;
&lt;P&gt;try as suggested use UTF8_bin&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/charset-unicode-sets.html" target="_self" rel="nofollow noopener noreferrer"&gt;https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-sets.html&lt;/A&gt;&lt;/P&gt;
&lt;PRE&gt;To further illustrate, the following equalities hold in both utf8_general_ci and utf8_unicode_ci (for the effect of this in comparisons or searches, see Section 10.1.8.6, “Examples of the Effect of Collation”):

Ä = A
Ö = O
Ü = U
A difference between the collations is that this is true for utf8_general_ci:

ß = s
Whereas this is true for utf8_unicode_ci, which supports the German DIN-1 ordering (also known as dictionary order):

ß = ss&lt;/PRE&gt;</description>
    <pubDate>Mon, 07 Aug 2017 23:20:41 GMT</pubDate>
    <dc:creator>vapukov</dc:creator>
    <dc:date>2017-08-07T23:20:41Z</dc:date>
    <item>
      <title>tMySqlOutput use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371544#M134466</link>
      <description>&lt;P&gt;Morning All,&lt;/P&gt; 
&lt;P&gt;I use tMySqlOutput to creat a new table and insert also records.&lt;/P&gt; 
&lt;P&gt;My primary Key column is VARCHAR type and everything is OK&lt;/P&gt; 
&lt;P&gt;But only one problem i get; Talend detect &amp;nbsp;these 2 lines (PK) like the same thing&lt;/P&gt; 
&lt;UL&gt; 
 &lt;LI&gt;&lt;SPAN&gt;ANA&lt;FONT color="#FF0000"&gt;E&lt;/FONT&gt;LLE.GUERIN&lt;/SPAN&gt;&lt;/LI&gt; 
 &lt;LI&gt;&lt;SPAN&gt;ANA&lt;FONT color="#FF0000"&gt;Ë&lt;/FONT&gt;LLE.GUERIN&lt;/SPAN&gt;&lt;/LI&gt; 
&lt;/UL&gt; 
&lt;P&gt;&lt;SPAN&gt;So i get this error:&lt;/SPAN&gt;&lt;/P&gt; 
&lt;PRE&gt;tMysqlOutput_1 - Duplicate entry 'ANAËLLE.GUERIN' for key 'PRIMARY'
Duplicate entry 'Céline.PHILIPPON.ERANOVE' for key 'PRIMARY'&lt;/PRE&gt; 
&lt;P&gt;&lt;SPAN&gt;I have already try this both collation utf8-general-ci and ut8-unicode-ci but nothing.&lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;Thank you help,&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 18:43:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371544#M134466</guid>
      <dc:creator>idembel2</dc:creator>
      <dc:date>2017-08-07T18:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: tMySqlOutput use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371545#M134467</link>
      <description>&lt;P&gt;Depending on the character set you have choosen for the database, you may try to create the column using:&lt;/P&gt;
&lt;PRE&gt;yourColumnName varchar(80) collate utf8_bin&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 22:13:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371545#M134467</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2017-08-07T22:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: tMySqlOutput use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371546#M134468</link>
      <description>&lt;P&gt;it is not a Talend issue, this is relate to MySQL and it's support of UTF (and error text - not from Talend, but from MySQL)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so, the proper place for search the answer - database related forums&lt;/P&gt;
&lt;P&gt;as, example -&amp;nbsp;&lt;A href="https://stackoverflow.com/questions/6466901/mysql-distinction-between-e-and-é-e-acute-unique-index" target="_self" rel="nofollow noopener noreferrer"&gt;https://stackoverflow.com/questions/6466901/mysql-distinction-between-e-and-é-e-acute-unique-index&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VARCHAR is always not best idea as Primary Key, but&amp;nbsp;&lt;/P&gt;
&lt;P&gt;try as suggested use UTF8_bin&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/charset-unicode-sets.html" target="_self" rel="nofollow noopener noreferrer"&gt;https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-sets.html&lt;/A&gt;&lt;/P&gt;
&lt;PRE&gt;To further illustrate, the following equalities hold in both utf8_general_ci and utf8_unicode_ci (for the effect of this in comparisons or searches, see Section 10.1.8.6, “Examples of the Effect of Collation”):

Ä = A
Ö = O
Ü = U
A difference between the collations is that this is true for utf8_general_ci:

ß = s
Whereas this is true for utf8_unicode_ci, which supports the German DIN-1 ordering (also known as dictionary order):

ß = ss&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Aug 2017 23:20:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371546#M134468</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2017-08-07T23:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: tMySqlOutput use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371547#M134469</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thank all for help, i test it and let you know&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 15:21:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371547#M134469</guid>
      <dc:creator>idembel2</dc:creator>
      <dc:date>2017-08-11T15:21:48Z</dc:date>
    </item>
    <item>
      <title>Re: tMySqlOutput use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371548#M134470</link>
      <description>Hello All,&lt;BR /&gt;&lt;BR /&gt;Thank you very much, Set Column as Utf8_bin solve my problem&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
      <pubDate>Tue, 15 Aug 2017 22:20:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tMySqlOutput-use-case/m-p/2371548#M134470</guid>
      <dc:creator>idembel2</dc:creator>
      <dc:date>2017-08-15T22:20:22Z</dc:date>
    </item>
  </channel>
</rss>

