Backup and restore is not MT safe when using the Services API [CORE1911] #2342
Labels
affect-version: 1.0.3
affect-version: 1.5.4
affect-version: 1.5.5
affect-version: 1.5.6
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.0.4
affect-version: 2.0.5
affect-version: 2.1 Alpha 1
affect-version: 2.1 Beta 1
affect-version: 2.1 Beta 2
affect-version: 2.1 RC1
affect-version: 2.1 RC2
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.5 Alpha 1
affect-version: 2.5 Beta 1
affect-version: 2.5 Initial
affect-version: 2.5.0
component: engine
component: gbak
fix-version: 2.5 Alpha 1
priority: major
type: bug
Submitted by: Claudio Valderrama C. (robocop)
Assigned to: Claudio Valderrama C. (robocop)
Backup and restore and never been MT-safe because the switches table is global. Activating options will toggle the field in_sw_state for the respective row in the switches table. If more than one attachment is backing up or restoring a db using the Services API, the options will mix, creating a mess. Whereas restoring a backup to the same db is an error, it's perfectly legal that diferent attachments make simultaneous backups of different databases via the Services API. The bug affects mainly SuperServer and the incoming SuperClassic.
Commits: 73994d2 6a439b2
The text was updated successfully, but these errors were encountered: