The Definitive Guide to Data Quality
Could you please review the way how "commit every..." data appears on the tXXXOutput? We only use existing connection and still need to use "commit every..." functionality in our Talend script. If we would like not to commit data for the existing connection - we'll just create a new one. I think it is really important to show "commit every..." on all tXXXOutput. Maybe we could add a warning messsage that it may have a problem with the existing connection if it is used for multiple tables simultaneously.
Yes, yesterday while reviewing your forum posts and bugtracker requests, I've thought about to this issue. I was about to implement it (in the tOracleCommit) but I saw your last note about having the option back in tOracleOutput.
I admit I don't know what the right choice is. I find it weird to let the tOracleOutput manage the commit while the transaction was opened in the tOracleConnection. I have in mind the following case : you have 2 tOracleOutput components in 2 output branches of a tMap. If the tOracleOutput_1 has a "commit every" set to 1000, it will also commit lines of tOracleOutput_2. On the other side, if we had a tOracleCommit ("commit every" set to 1000) right after the tOracleOutput_1, it doesn't make the design much cleaner.