You can translate the question and the replies:

Weird dependency name in COLUMN_DEPENDENCIES() stored procedure

Hi all, I have a problem when executing COLUMN DEPENDENCIES() procedure. I had a derived view with just one column coming from a web service base view and I have modified the model and the output to add another derived view, and now when calling the procedure, the dependency name for the initial column has changed from the name of the source view to: _incidents_p_internet_inc_4187316971463725048238318594553495366231595661_4710518436 Any idea why this is happening and/or how to avoid/fix it? It would be much appreciated. Thank you!
24-10-2018 09:59:35 -0400

1 Answer

Hi, This kind of view name shows up automatically when Denodo creates a temporary view during a join, leading to a dependency on that temporary view, and the weird name. There’s no real way to avoid it, but it’s not indicative of anything fishy. Hope this helps!
Denodo Team
01-11-2018 18:14:44 -0400
You must sign in to add an answer. If you do not have an account, you can register here