<?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 Exasol mixed case column names in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Exasol-mixed-case-column-names/m-p/2322976#M92875</link>
    <description>&lt;P&gt;Dear community,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;When using mixed case column names in Talend and&amp;nbsp;tEXAOutput component I noticed that I need to modify the Db Column metadata for &lt;STRONG&gt;each&lt;/STRONG&gt; column in the table by wrapping it in escaped double quotes in order to generate valid INSERT statements via Talend Data Integration.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For example if the column name is:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Exasol_Column_Name&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then the Db Column must be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;\"Exasol_Column_Name\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a simpler and more automated way to achieve valid INSERT statements?&lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;This problem first was reported in 2013 related to Oracle components. Then again in 2018 (see links below). &lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;UL&gt; 
 &lt;LI&gt;&lt;SPAN&gt;&lt;A href="https://community.qlik.com/s/feed/0D53p00007vCrDTCA0#M71751" target="_blank" rel="noopener"&gt;https://community.talend.com/t5/Design-and-Development/Oracle-Mixed-case-column-names/m-p/114205/highlight/true#M71751&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt; 
 &lt;LI&gt;&lt;SPAN&gt;&lt;A href="https://community.qlik.com/s/feed/0D53p00007vCs7wCAC#M2302" target="_blank" rel="noopener"&gt;https://community.talend.com/t5/Data-Quality-Preparation-and/Mixed-case-columns-in-Oracle-fail-to-analyze/m-p/120550#M2302&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt; 
&lt;/UL&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;So what can we do here? When will you fix this issue? Sorry to say but this is definitely a&amp;nbsp;showstopper when you want to use Talend in order to integrate data from Oracle and/or EXASOL.&lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;Pleas don't ignore this issue (any more)!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 03:12:14 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T03:12:14Z</dc:date>
    <item>
      <title>Exasol mixed case column names</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Exasol-mixed-case-column-names/m-p/2322976#M92875</link>
      <description>&lt;P&gt;Dear community,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;When using mixed case column names in Talend and&amp;nbsp;tEXAOutput component I noticed that I need to modify the Db Column metadata for &lt;STRONG&gt;each&lt;/STRONG&gt; column in the table by wrapping it in escaped double quotes in order to generate valid INSERT statements via Talend Data Integration.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For example if the column name is:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Exasol_Column_Name&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then the Db Column must be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;\"Exasol_Column_Name\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a simpler and more automated way to achieve valid INSERT statements?&lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;This problem first was reported in 2013 related to Oracle components. Then again in 2018 (see links below). &lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;UL&gt; 
 &lt;LI&gt;&lt;SPAN&gt;&lt;A href="https://community.qlik.com/s/feed/0D53p00007vCrDTCA0#M71751" target="_blank" rel="noopener"&gt;https://community.talend.com/t5/Design-and-Development/Oracle-Mixed-case-column-names/m-p/114205/highlight/true#M71751&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt; 
 &lt;LI&gt;&lt;SPAN&gt;&lt;A href="https://community.qlik.com/s/feed/0D53p00007vCs7wCAC#M2302" target="_blank" rel="noopener"&gt;https://community.talend.com/t5/Data-Quality-Preparation-and/Mixed-case-columns-in-Oracle-fail-to-analyze/m-p/120550#M2302&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt; 
&lt;/UL&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;So what can we do here? When will you fix this issue? Sorry to say but this is definitely a&amp;nbsp;showstopper when you want to use Talend in order to integrate data from Oracle and/or EXASOL.&lt;/SPAN&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN&gt;Pleas don't ignore this issue (any more)!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 03:12:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Exasol-mixed-case-column-names/m-p/2322976#M92875</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T03:12:14Z</dc:date>
    </item>
  </channel>
</rss>

