|
|
|
[
Permlink
| « Hide
]
Siim Käba [29/May/12 05:00 PM]
Sorry, you probably see that my summary is wrong in this description context. I will create another bug when i have more information about the deadlocks during configuration delete, there a many of them.
It seems that some foreign key constraints have been violated in database. I guess you are using MyISAM as MySQL storage engine for QuickBuild database. If so, please switch to InnoDB engine which will enforce foreign key constraints.
Yes, you are right. QB tries to delete all builds before deleting the configuration. However in rare cases, a new build might comes in just after QB deleted all existing builds for the configuration, and subsequent deletion of the configuration can result this error. We could have locked the whole deletion process so that no new builds will be created, but the lock might be expensive. So for these rare cases, we just leave it to database to report the error.
Upon such cases, the configuration can normally be deleted successfully if you try to delete again.
|