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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

How to change the column name from UPPER case to lower case without using tMap

I'm trying to import data from MySQL to PostgreSQL but seems there is a case sensitive issue with column names.
MySQL has:
Id | OrgId | EmailID

PostgreSQL has:
id | orgid | emailid

To make it easy for Talend, I selected column names renaming them to lowercase in the tDBInput and then added them to tDBOutput
" select Id as id,OrgId as orgid,EmailId as emailid from employee "

However, it still fails with below error
ERROR: column "Id" of relation "employee" does not exist

 

I was dumping data from 75 tables and do not want to create views or tMap(this components seems staging data and takes longer time).
Is there any other way to achieve this using Talend Open Studio 7.0.1?

Labels (2)
15 Replies
Anonymous
Not applicable
Author

Your change earlier where you noticed that after casting the value the error moved on to the next column, seems to suggest that your source types are different to your target types. Can you add a tMap and see if this solves this?

Anonymous
Not applicable
Author

@rhall

Yes, adding a tMap solves the issues. Doesn't tMap stage the data before loading to destination which may be a performance hiccup?

Anonymous
Not applicable
Author

No, the tMap doesn't stage the data. Everything is done in memory by default. You CAN store it, but unless you are working with lots of lookups over millions of rows, there is no point. The scenario you have described here doesn't sound like you would need to do that.

 

What performance issues are you seeing? I have never seen performance issues caused by a simple pass-through tMap 

Anonymous
Not applicable
Author

@rhall

I have no evidence on performance issues. Its just my assumption.

Anonymous
Not applicable
Author

OK. Just use the tMap solution then. You will not see any performance problems doing it this way

Anonymous
Not applicable
Author

@rhall

Thank you