• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Input Backup and restore of MySQL database should handle correctly views

carini

Basic Pleskian
When attempting to restore databases, the process fails to recreate database views. This seems to be a significant oversight in the restoration functionality (see support request Id #95245922)

During a database restore procedure, all table data is correctly reinstated; however, views are not being recreated. The expectation for a restoration process is a complete replication of the original database state, which includes tables, views, stored procedures, etc. Currently, the absence of views post-restoration necessitates manual intervention, which is not feasible in scalable environments.

Storing and subsequently executing the SQL queries used to create views during the backup phase is entirely feasible. Implementing this would ensure that views are restored accurately, maintaining the integrity and utility of the database post-recovery.
 
Issue has not be recognised as a bug as per Id #95245922. So I opened the request for future improvement.
 
Back
Top