Update table schema from db does not work

One Star

Update table schema from db does not work

Hi,
I am running Talend 4.1.2.
When a table's schema in the db has changed, I want to have this easily reflected in my repository metadata... So I right-click the corresponding table in the metadata tree and choose Edit Schema. Next, in the dialog, I click the Retrieve Schema button.
The problem is that the old schema is not being updated with the new schema, but instead an empty list appears. Is this a bug, or do I have to manually alter the schema in the repository then?
Thanks,
Yves
One Star

Re: Update table schema from db does not work

Hi Pedro,
Thanks, I'll update (as soon as I can spare the time today) and report back if I would still encounter the issue.
Kind regards,
Yves
One Star

Re: Update table schema from db does not work

Hi
I reproduced this issue in TOS 4.2.3. Schemas are updated automatically atfer retrieving schema again.
I strongly recommend that you update your TOS to version 4.2.3 or 5.0.
But you need to correct query of tXXXInput.
Best regards!
Pedro
One Star

Re: Update table schema from db does not work

I have the same problem as Yves does in 4.2.3
I upgraded to 5.0, and the same problem exists.
I've even deleted the table schema from my metadata, and tried to reload it, but Talend says:
Another 'table' already exists in "MyDbName". Do you want to cover it?
So I click "yes", but it does not re-read the table.
Am I doing something wrong? Please advise.
- Mark
One Star

Re: Update table schema from db does not work

Hi Mark
Could you show me your OS version?
In addition, please upload the screenshot of your issue.
Then i can make sure whether it's a bug.
Best regards!
Pedro
One Star

Re: Update table schema from db does not work

Same problem with 4.2.3r67267
When update a table in the database (SQLServer2008, with a MicrosoftSqlServer native connection) and wish update the schema - sometimes work fine (the old schema is updated with the new one), sometimes not (an empty list appears).
The only way is then delete the schema, empty the trash and reload the schema again. :-/
(it works fine in the previous version 4.1.1)