Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Why is the default mapping of TINYINT to Boolean in MySQL?

Hi All,
I'm loading Data MySQL to MySQL.In source one filed datatype is TINYINT,in Talend by default it's taking Boolean data type.
Talend doesn't support TINYINT datatype?
Regards,
kumar
Labels (2)
7 Replies
Anonymous
Not applicable
Author

hi,
TINYINT is a DB type. Talend has a default behavior defined by data xml file  mapping (metadata of talend type).
@see window => preferences => specific setting
its tell us :
<dbType type="TINYINT">
                    <talendType type="id_Byte" default="true" />
                    <talendType type="id_Integer"/>
                    <talendType type="id_Long"/>
                    <talendType type="id_Short"/>
                </dbType>

db Type To java type (talend).
but it's the default behavior.
regards
laurent
_AnonymousUser
Specialist III
Specialist III

so i ended up trying to changed the default in the xml file to:
 <dbType type="TINYINT">
 <talendType type="id_Short"  default="true"/>
 <talendType type="id_Integer"/>
 <talendType type="id_Long"/>
 </dbType>

restarted my studio and then tried to see if the default mapping changed ... and it still doesn't for me - what am i doing wrong?
Anonymous
Not applicable
Author

Hi hansolo
After you change the mapping setting, try to retrieve a table schema that contains a field with TINYINT type, you will see the DB type is "Short".
0683p000009MDBT.png
Best regards
Shong
_AnonymousUser
Specialist III
Specialist III

nope - that did not happen for me.  
Anonymous
Not applicable
Author

Which version are you using? If it does not display the right db type, try to click the Retrieve Schema button again.
hson
Contributor
Contributor

i am using Version: 5.5.1
Build id: r118616
hitting that button doesn't help for me.
Anonymous
Not applicable
Author

I tested it in v6.0 and it works, maybe it was a bug on v5.5.1, I would suggest you to test it also in the latest versions.