<?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: MySQL / MariaDB Schema Retrieval for TINYINT being detected as BIT - RESOLVED in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/MySQL-MariaDB-Schema-Retrieval-for-TINYINT-being-detected-as-BIT/m-p/2339517#M107650</link>
    <description>&lt;P&gt;To apply this option in Talend, edit your connection details, in Additional Parameters, enter&lt;/P&gt;&lt;P&gt;tinyInt1isBit=false&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Apr 2023 02:30:57 GMT</pubDate>
    <dc:creator>BraidwoodIT</dc:creator>
    <dc:date>2023-04-05T02:30:57Z</dc:date>
    <item>
      <title>MySQL / MariaDB Schema Retrieval for TINYINT being detected as BIT - RESOLVED</title>
      <link>https://community.qlik.com/t5/Talend-Studio/MySQL-MariaDB-Schema-Retrieval-for-TINYINT-being-detected-as-BIT/m-p/2339516#M107649</link>
      <description>&lt;P&gt;I have a MySQL database with a heap of TINYINT columns  (it's a Moodle Database). Many of these columns have values in the range of 0,1,2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I use Talend Open Studio 7.4.1 (was same on 6.4 too), it detects these TINYINT columns as BIT/Boolean. In most cases it works as the '2' values are few and far between but in some tables it's a problem. I have been manually modifying the repository schema, changing the columns to Short|SMALLINT as trying to change to Short|TINYINT was throwing errors about dbtype.  The problem with this approach is that I have to remember that the schema in the repository isn't the same as the actual schema and if I update the schema from the database at a later date, I might not remember I have to change all those BITS to TINYINT|Short&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Today I finally found the solution. The fact that the schema retrieval detects the TINYINT as a BIT is due to a 'feature' in jdbc.  There is an option in jdbc to make it detect the column as TINYINT.&lt;/P&gt;&lt;P&gt;To apply this option in Talend, edit your connection details, in Additional Parameters,  enter &lt;/P&gt;&lt;P&gt;tinyInt1isBit=false&lt;/P&gt;&lt;P&gt;Now you need to retrieve all your schemas again and the changes will flow thru.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps someone&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2024 21:55:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/MySQL-MariaDB-Schema-Retrieval-for-TINYINT-being-detected-as-BIT/m-p/2339516#M107649</guid>
      <dc:creator>BraidwoodIT</dc:creator>
      <dc:date>2024-11-15T21:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL / MariaDB Schema Retrieval for TINYINT being detected as BIT - RESOLVED</title>
      <link>https://community.qlik.com/t5/Talend-Studio/MySQL-MariaDB-Schema-Retrieval-for-TINYINT-being-detected-as-BIT/m-p/2339517#M107650</link>
      <description>&lt;P&gt;To apply this option in Talend, edit your connection details, in Additional Parameters, enter&lt;/P&gt;&lt;P&gt;tinyInt1isBit=false&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2023 02:30:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/MySQL-MariaDB-Schema-Retrieval-for-TINYINT-being-detected-as-BIT/m-p/2339517#M107650</guid>
      <dc:creator>BraidwoodIT</dc:creator>
      <dc:date>2023-04-05T02:30:57Z</dc:date>
    </item>
  </channel>
</rss>

