When you deploy an update the database views will get deleted and recreated by the installation workflow in the installer (as far is I understand).
The context of these questions is a customer who want’s to know how changes in fields and functions (renames and drops) affect the database views, because they use the database views in their datawarehouse.
What does the installer workflow exactly do with the databse views? Does every view get deleted and created again after installation?
When a function in a component has it’s name and logic changed how does that affect the views?
When a function or field is removed in the update how does this proces change the database views?
The views are created to allow functions that are defined in Novulo expressions (as defined in the Architect) to be easily used in SQL. Views are created for every type, containing all their fields, and all parameterless functions that can be executed in SQL. The original use case was to be able to use them in Microsoft SSRS. This way, the reports would always follow changes that were made to the application automatically and show information that is consistent with what you would see in the application.
To answer your questions:
1: Before updating the application code, the views are deleted (based on the types registered in that version of the application), and after updating, they are recreated (based on the new version). Note: there is a possibility that some views are not deleted properly when updating an application is ‘mixed’ with replacing the database with one that belongs to a different application revision - the views that are defined in that database might not match the types registered in the before-installation version of the application.
2&3: The views will reflect those changes after the update.