We have functions that use views and views that use functions which leads to incorrect upgrade scripts in the deploy packages which in turn leads to upgrade errors when trying to upgrade a system. This has a significant impact on the time that is needed to create, deploy and execute the deploy package successfully
When changes are (being) made on a view and the view is used in a function is something that can lead to upgrade errors on ‘FUNCTIONS’ because the changed ‘VIEW’ must be available in the system before the function can be implemented. Same the other way around when a function is changed and is used within a view. This also occurs when tables are changed that are used in a view.
We would like to see that the deploy mechanism takes care of this situation and results in a deploy package that manages the dependencies between views and functions, and tables and views.
The ability to manage this would be a massive help when upcycling legacy applications.
In a new application I would try to avoid these dependencies as much as possible.