• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Error while backup 'pkg.release as release'

G

guesswho911

Guest
About the middle of the month we changed our license to allow for Application Repo to be active. We didn't think anything of it until we went to look for our backups and found that they haven't been successful for a while. They seem to be coming up with this in the error:

Backup error.
Can't query SELECT pkg.name as name, pkg.version as version, pkg.release as release FROM APSApplicationItems ai INNER JOIN siteapppackages pkg ON ai.pkg_id=pkg.id WHERE ai.id=90: MySQLDatabaseProvider error 1064:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'release FROM APSApplicationItems ai INNER JOIN siteapppackages pkg ON ai.pkg_' at line 1

However if I run the command in mysql:
SELECT pkg.name as name, pkg.version as version, pkg.release as 'release' FROM APSApplicationItems ai INNER JOIN siteapppackages pkg ON ai.pkg_id=pkg.id WHERE ai.id=90

That command works. Apparently release is a reserved keyword in MySQL 5.0 but it is causing a problem in the script. Has anyone else run into this issue before and perhaps knows how to possibly solve it as it seems to be impossible to do a backup otherwise?
 
Back
Top