topic Re: tDBInput and ODBC in Talend Studio

tDBInput and ODBC

_AnonymousUser — Sat, 16 Nov 2024 14:23:39 GMT

Hi,
tDBInput is used to read in all kind of databases. But, is it work only with ODBC ?
Regards,
Caroline

Re: tDBInput and ODBC

Anonymous — Thu, 17 Apr 2008 13:38:01 GMT

yes, tDBInput uses ODBC
tJDBC allow generic connexion trough JDBC
What would you like to do ?

Re: tDBInput and ODBC

_AnonymousUser — Thu, 17 Apr 2008 15:35:59 GMT

I would like to use a component capable to read all kind of databases (thus user can use context variables to enter his database connection).

Re: tDBInput and ODBC

Anonymous — Thu, 17 Apr 2008 19:56:52 GMT

I don't really understand what you reall wants to do.
All your databases have the same tables with the same columns ?

Re: tDBInput and ODBC

_AnonymousUser — Mon, 02 Jun 2008 09:50:32 GMT

I to have something similar in mind, but not different databases. I would like it if I could change the IP address of my database connections with a variable field you can change on setup if you wan to.
Cheers
qunu

Re: tDBInput and ODBC

Anonymous — Mon, 02 Jun 2008 18:12:48 GMT

You can easily do this in Talend.
Just define your context variables and use them as parameters in your tXXXInput, tXXXOutput, tXXXRow components.
I've posted some examples.

Re: tDBInput and ODBC

Anonymous — Mon, 07 Jul 2008 08:59:42 GMT

Hello,
i have in a string field a date in this format String ( 02/01/1900 00:00:00)
I would like to have it like yyyy-mm-dd in an output field (in string)
I use a Tmap1 and i want to include in it.
I've try TalendDate.formatDate("yyyy/MM/dd 00:00:00",TalendDate.parseDate("yyyy-MM-dd",row1.dateemission)), but i can't get a good result
Exception in component tMap_1
java.lang.RuntimeException: java.text.ParseException: Unparseable date: "02/01/1900 00:00:00"
at routines.TalendDate.parseDate(TalendDate.java:87)
at blueprint.ekb_p112_expertbo_ais_date.EKB_P112_ExpertBO_AIS_date.tFileInputDelimited_1Process(EKB_P112_ExpertBO_AIS_date.java:947)
at blueprint.ekb_p112_expertbo_ais_date.EKB_P112_ExpertBO_AIS_date.runJobInTOS(EKB_P112_ExpertBO_AIS_date.java:3245)
at blueprint.ekb_p112_expertbo_ais_date.EKB_P112_ExpertBO_AIS_date.main(EKB_P112_ExpertBO_AIS_date.java:3161)
Caused by: java.text.ParseException: Unparseable date: "02/01/1900 00:00:00"
at java.text.DateFormat.parse(Unknown Source)
at routines.TalendDate.parseDate(TalendDate.java:85)

Thanks

Re: tDBInput and ODBC

Anonymous — Mon, 07 Jul 2008 09:23:53 GMT

Hello,
Try this way :
TalendDate.formatDate("yyyy-MM-dd",TalendDate.parseDate("dd/MM/yyyy HH:mm:ss",row1.dateemission))
It works well with row1.dateemission = 02/01/1900 00:00:00
JC

Re: tDBInput and ODBC

_AnonymousUser — Mon, 10 Nov 2008 23:01:16 GMT

Hate to dig up an old thread, but this is really bothering me.
If I have already created a context in the repository and imported it into my job, how do I then create an additional context and use the same steps to configure two different contexts?
When I try to do this using the button on the lower left of the Variables tab under Contexts, it shows me the context in the popup but shows nothing when I try to expand it and select the variables.
If you don't create all your contexts before importing the vars in your job you can't use this feature?