<?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: UTF-8 character encoding problem with mysql in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375023#M137528</link>
    <description>Hi,
&lt;BR /&gt;I have added "useUnicode=true&amp;amp;characterEncoding=UTF-8" in the additional parameter of tMysqlOutput component.
&lt;BR /&gt;I am also trying to output data from tMysqlInput component into tLogrow, but it doesnot show UTF-8 there either.
&lt;BR /&gt;Also I recreated the table with below syntax.
&lt;BR /&gt;CREATE TABLE `temp_utf8` (
&lt;BR /&gt; `id` bigint(10) NOT NULL,
&lt;BR /&gt; `title` varchar(128) NOT NULL
&lt;BR /&gt;) ENGINE=InnoDB DEFAULT CHARSET=utf8;
&lt;BR /&gt;Still I am facing the same problem.
&lt;BR /&gt;I am sure I am missing something here.
&lt;BR /&gt;Regards,
&lt;BR /&gt;Saabir</description>
    <pubDate>Thu, 22 Aug 2013 11:45:28 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2013-08-22T11:45:28Z</dc:date>
    <item>
      <title>UTF-8 character encoding problem with mysql</title>
      <link>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375020#M137525</link>
      <description>Hi,
&lt;BR /&gt;I am using talend v 5.3, I have followed all the steps mentioned below.
&lt;BR /&gt;i.e. added "useUnicode=true&amp;amp;characterEncoding=UTF-8" in the additional parameter of the mysql connection.
&lt;BR /&gt;also tried "SET character_set_results = 'utf8', character_set_client = 'utf8', character_set_connection = 'utf8', character_set_database = 'utf8', character_set_server = 'utf8'" in the mysql row component but I am still facing this problem.
&lt;BR /&gt;I was trying to use the traces debug and found that the strings are not getting converted to UTF-8 format.
&lt;BR /&gt;Is this a problem in the v5.3 or have I missed anything in the above statements. Please check the attached images.
&lt;BR /&gt;Regards,
&lt;BR /&gt;Saabir</description>
      <pubDate>Wed, 21 Aug 2013 11:37:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375020#M137525</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-08-21T11:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: UTF-8 character encoding problem with mysql</title>
      <link>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375021#M137526</link>
      <description>Hi, 
&lt;BR /&gt; 
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;
 &lt;TABLE border="1"&gt;
  &lt;TBODY&gt;
   &lt;TR&gt;
    &lt;TD&gt;i.e. added "useUnicode=true&amp;amp;characterEncoding=UTF-8" in the additional parameter of the mysql connection.&lt;/TD&gt;
   &lt;/TR&gt;
  &lt;/TBODY&gt;
 &lt;/TABLE&gt;
&lt;/BLOCKQUOTE&gt;
&lt;BR /&gt;Why didn't you add the additional parameter in tMysqlOutPut component. How did you design your workflow.
&lt;BR /&gt;Best regards
&lt;BR /&gt;Sabrina</description>
      <pubDate>Thu, 22 Aug 2013 04:06:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375021#M137526</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-08-22T04:06:37Z</dc:date>
    </item>
    <item>
      <title>Re: UTF-8 character encoding problem with mysql</title>
      <link>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375022#M137527</link>
      <description>Please check the charset settings of your table. The default for it after creating a table without any given option is Swedish! It is to late changing the database settings after the table is already created.&lt;BR /&gt;If you have changed the language/charset option for your database you can consider drop table and create it new (e.g. by Talend output components). In this case - after the database has the uft8 charset - all new tables take this as default charset.&lt;BR /&gt;In your Talend job you have actually no real influence to this topic.</description>
      <pubDate>Thu, 22 Aug 2013 07:34:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375022#M137527</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-08-22T07:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: UTF-8 character encoding problem with mysql</title>
      <link>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375023#M137528</link>
      <description>Hi,
&lt;BR /&gt;I have added "useUnicode=true&amp;amp;characterEncoding=UTF-8" in the additional parameter of tMysqlOutput component.
&lt;BR /&gt;I am also trying to output data from tMysqlInput component into tLogrow, but it doesnot show UTF-8 there either.
&lt;BR /&gt;Also I recreated the table with below syntax.
&lt;BR /&gt;CREATE TABLE `temp_utf8` (
&lt;BR /&gt; `id` bigint(10) NOT NULL,
&lt;BR /&gt; `title` varchar(128) NOT NULL
&lt;BR /&gt;) ENGINE=InnoDB DEFAULT CHARSET=utf8;
&lt;BR /&gt;Still I am facing the same problem.
&lt;BR /&gt;I am sure I am missing something here.
&lt;BR /&gt;Regards,
&lt;BR /&gt;Saabir</description>
      <pubDate>Thu, 22 Aug 2013 11:45:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/UTF-8-character-encoding-problem-with-mysql/m-p/2375023#M137528</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-08-22T11:45:28Z</dc:date>
    </item>
  </channel>
</rss>

