Dirty tracks cause incorrect sorting and searching
Bug #700802 reported by
Owen Williams
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Medium
|
RJ Skerry-Ryan | ||
1.10 |
Fix Released
|
Medium
|
RJ Skerry-Ryan | ||
1.9 |
Fix Released
|
Medium
|
RJ Skerry-Ryan |
Bug Description
If I make changes to track metadata (retitling, or changing the comment, etc), subsequent searches of the library don't reflect the new values. This is because the search function only uses the database, not the dirty track data.
The fix for this bug is either:
* rewrite the search function to look through the dirty tracks (hard coding but fast execution)
* save dirty tracks before performing the search (easy coding but whacks the DB)
Related branches
lp:mixxx/1.9
(Merged)
summary: |
- database searches don't reflect dirty track updates + Dirty tracks cause incorrect sorting and searching |
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in mixxx: | |
status: | Confirmed → Fix Committed |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixing searching and sorting to defer to the track cache is pretty hard given the way things work now sadly. Correctness has a pretty big cost in this case. Every single track gets dirtied now on load b/c it is marked played, so on a sort or search we have to save ~50 tracks if the cache is full.