Improve robustness of upgrade script for legacy applications
In case, an installation has the legacy view (must be from very old installations) in place, it is necessary to drop it before registered_users, otherwise PostgreSQL will complain that it cannot drop view registered_users because other objects depend on it.
Many thanks to Franz Penz to report this potential problem for old sites.
Fixed update script for applications having the view "upgrade-5.10.0-5.10.1d1.sql" not defined.
This view is a legacy view ancient times, which is no included in standard installations since ages.... It was however defined on openacs.org.
-- -- Some legacy applications might contain still the VIEW -- "registered_users_of_package_id", which is defined in -- -- acs-subsite/sql/postgresql/user-profiles-create.sql -- -- This file is NOT included in new installations since over 20 years, -- so it is not maintained and treated as a leftover from ancient -- times. Therefore, the view registered_users_of_package_id is not -- recreated by this update script.