• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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