Inconsistent database: LibraryScanner

Bug #1846971 reported by Uwe Klotz
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

Due to various bugs and inconsequent usage of transactions the Mixxx database accumulates inconsistent entries over time. Those inconsistent contents cause consecutive bugs:

How-to-fix: Periodically (e.g. after upgrading the database schema on startup) remove inconsistent rows from all tables for which the referential integrity constraints are violated.

Changed in mixxx:
milestone: 2.2.3 → none
assignee: Uwe Klotz (uklotzde) → nobody
status: In Progress → New
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Fix only inconsistencies caused by LibraryScanner:

Changed in mixxx:
milestone: none → 2.2.3
assignee: nobody → Uwe Klotz (uklotzde)
status: New → In Progress
summary: - Inconsistent database
+ Inconsistent database: LibraryScanner
description: updated
Changed in mixxx:
status: In Progress → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.