After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 560862 - Compilation albums should be listed only once in the album list
Compilation albums should be listed only once in the album list
Status: RESOLVED DUPLICATE of bug 557313
Product: banshee
Classification: Other
Component: User Interface
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-14 22:09 UTC by John Millikin
Modified: 2008-11-15 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Create only one database entry for compilation albums (1.98 KB, patch)
2008-11-14 23:31 UTC, John Millikin 		none Details | Review

Description John Millikin 2008-11-14 22:09:40 UTC 
If an album has multiple artists, it will be listed twice in the album list. The two entries are visually identical, but when clicked display a different selection of tracks.

Instead, each album should be listed only once, and clicking it should contain all tracks for that album.
Comment 1 John Millikin 2008-11-14 23:31:50 UTC 
Created attachment 122702 [details] [review]
Create only one database entry for compilation albums

Turns out the issue was actually in the database, rather than GUI, layer. If a compilation album is imported, it will have multiple entries created; one with IsCompilation = 0, and the other = 1.

This patch modifies the `DatabaseAlbumInfo.FindOrCreate` method, so that if it finds an existing album that differs only in the IsCompilation flag, it will update the saved album.
Comment 2 Bertrand Lorentz 2008-11-15 11:54:32 UTC 
Just to clarify things : the files you imported had different values for the IsCompilation tag in their metadata ?
Comment 3 Wouter Bolsterlee (uws) 2008-11-15 14:22:33 UTC 
557313

*** This bug has been marked as a duplicate of 557313 ***