| Anonymous | Login | Signup for a new account | 2010-09-03 07:38 CEST |
| Main | My View | View Issues | Change Log | Roadmap | Summary | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0002063 | [Talend Open Studio] Perl components | feature | always | 2007-09-21 10:46 | 2008-01-09 23:40 | ||
| Reporter |
pemen |
View Status | public | ||||
| Assigned To | |||||||
| Priority | normal | Resolution | fixed | Platform | |||
| Status | closed | OS | |||||
| Projection | none | OS Version | |||||
| ETA | none | Fixed in Version |
2.3.0M2
|
Product Version | |||
| Target Version | Product Build | ||||||
| Summary | 0002063: [tMysqlOutput] update key different from primary key | ||||||
| Description |
See this forum post for detail [Forum] topic 1350 The goal is to have different key for the insert mode and the update mode. For example the primary key for the insert mode and an alternative key (AK) for the update mode. This is a necessity in most of projects where tables contains technical primary key (with auto increment fields) and functional key (AK). And most of the time when you want to update a row, you know the AK (a functional code for example custumerCode) but not necessary the technical key. It would be a great feature for TALEND to compete with SUNOPSIS (for example) to manage these things instead of having simple Insert/update procedure. So 2 features are important : - Choose the update key for the update mode - Allow to choose for each field of the schema which field will be update. |
||||||
| Steps To Reproduce | |||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| generated language | perl, java | ||||||
| workload (in half days) | |||||||
| Attached Files |
|
||||||
|
|
|||||||
Relationships |
||||||
|
||||||
Notes |
|
|
(0004039) pemen (reporter) 2007-09-21 10:48 |
And also "Insertable field" like "Updatable field" |
|
(0004043) plegall (reporter) 2007-09-21 12:14 |
I think it's a great idea. I won't include these informations in the schema but in a based_on_schema table of tDB*Output. |
|
(0004044) pemen (reporter) 2007-09-21 12:34 edited on: 2007-09-21 16:28 |
Yes probably better to manage that in a dedicates structure. You can link this feature request with : [Bugtracker] feature 1841 Actually I have to add in my job the target table as a source in the job an make an inner join to manage insert and update separately. It's not good for performance and i think that TALEND has all the based functionnalities to do that. Hope this feature will be integrated rapidly in the next release !!! |
|
(0004046) pemen (reporter) 2007-09-21 14:00 |
It would be interesting to add the possibility in the metadata (manually or by reverse) to have additional keys (like AK, IDX). These new keys in metadata will be use to manage the key in UPDATE MODE. It's better to define this key in the metadata to be use in all jobs. |
|
(0004048) plegall (reporter) 2007-09-21 16:32 |
pemen (with a lot of hope) wrote: > Hope this feature will be integrated rapidly in the next release !!! We're sorry but no, we are really near 2.2.0 and it's too late to add such a fat feature (it is a fat feature in the code) |
|
(0004054) pemen (reporter) 2007-09-21 18:53 |
"We're sorry but no, we are really near 2.2.0 and it's too late to add such a fat feature (it is a fat feature in the code)" Yes I understand very well. Hope this will be included in the next release 2.3 ? |
|
(0005193) pemen (reporter) 2007-11-13 11:02 |
Any news about this issue for future realease 2.3.x ? |
|
(0005456) plegall (reporter) 2007-11-28 14:26 |
Added on trunk in [Subversion, tos] r7259. I've simplified the problem : I've coded a solution only for tMysqlOutput (my database output coding template). Pemen, I would be glad if you could tell me if it fits your need. Just activate the "field options". |
|
(0005457) pemen (reporter) 2007-11-28 14:48 |
In professonal uses I only work with MSSQL Components; but I can have a look at your commit in MYSQLOutput component and this new functionnality would be commit to MSSQL Components after that. I return to you soon |
|
(0005510) pemen (reporter) 2007-12-01 17:26 |
Waiting for 2.3 M2 for testing |
|
(0005575) plegall (reporter) 2007-12-05 10:08 |
Let's say it's resolved (so that the new feature appears in the ChangeLog) and we'll reopen it if needed for your feedback pemen. |
|
(0005936) pemen (reporter) 2007-12-31 13:52 |
I can't find how to choose for each field of the schema which field will be update. Is it implemented in this issue ? |
|
(0005937) plegall (reporter) 2007-12-31 14:27 |
pemen wrote: > I can't find how to choose for each field of the schema > which field will be update. In TOS 2.3.0M2, on a Perl project, check the "Use field options" checkbox. |
|
(0005938) pemen (reporter) 2007-12-31 15:34 |
Sorry I haven't seen, it was only in Perl. I have had a look and it looks good. I have not made a complete test but it is possible to manage Update/Insert and key for each field so we can make what we want. Good. I only work in Java. When this feature will be release in Java components (MSSQL Components at least)? |
|
(0006039) pemen (reporter) 2008-01-08 08:49 |
Is it possible to implement what has been done in PERL in a JAVA component, for example MSSQL components in order for me to test the functionality. I have a lot of use case for testing it. |
|
(0006044) plegall (reporter) 2008-01-08 10:34 |
pemen, I suggest you to clone this feature request and to set the category to "Java components" |
|
(0006045) plegall (reporter) 2008-01-08 10:39 |
pemen wrote: > I have had a look and it looks good. So I close this entry. |
| Mantis 1.1.6[^] Copyright © 2000 - 2007 Mantis Group |