Fortunately, release 5.1.46 of MySQL now is able to properly dump databases containing the VIEWs we need. MySQLDump now creates an SQL file that can be properly imported again. This makes our specialized backup procedure in ChartaWebBackup, that dumps BASE TABLEs only, unnecessary. We should phase out this specialized procedure.
Because views now can be properly dumped and imported again we should start treating views as ordinary database objects and create/drop them using database scripts. The method of creating views on the fly now is deprecated in general. Special cases might still call for views that are created on the fly.
Because currently quite a number of views are created on the fly and I wanted to rename three of them, I have limited myself to just renaming them in the code. This means that databases from before this change still will contain the old views. However, restoring a recent backup using ChartaWebBackup will get rid of these excess views.