When a Function returning a scalar is written in C, it is easy to
change the code, by just creating a new loadable object.

When the code is written in SQL procedure language, how to replace the
code when there are dependencies? The restrict is default in drop
function, there is no no-restrict capability.

Remark: was already posten in the newsgroups, concerning dependencies
on triggers. Suggestion was to drop and recreate the triggers. What if
the dependency impacts ... tables?

Bernard Dhooghe

Bernard Dhooghe wrote:[color=blue]
> When a Function returning a scalar is written in C, it is easy to
> change the code, by just creating a new loadable object.
>
> When the code is written in SQL procedure language, how to replace the
> code when there are dependencies? The restrict is default in drop
> function, there is no no-restrict capability.
>
> Remark: was already posten in the newsgroups, concerning dependencies
> on triggers. Suggestion was to drop and recreate the triggers. What if
> the dependency impacts ... tables?
>
> Bernard Dhooghe
>[/color]
You will need to unravel the dependencies and recreate the objcets
afterwards.
There is a function DB2LK_DEP_OF() which you can use to get the
dependencies sorted out.

Long term expect DB2 to introduce "invalid" states for all objects which
can be revalidated on first use.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

Thank you Serge.

I'll put it on my long-term-hope pile.

Bernard Dhooghe