• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff 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