View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001987 | MMW v4 | Playlist / Search | public | 2005-09-02 02:44 | 2010-10-25 14:32 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0001987: Advanced Search/AutoPlaylists: Query by Playlist | ||||
| Description | Some users in the forum have requested the ability to 'nest playlists' in a manner similar to how iTunes allows users to initiate queries based on Playlist membership, but in a way that users can create a playlist that contains members of playlists A or B, A and B, or A and not B. This can easily be accomplished by adding functionality to query by playlists and new logical operators described in bug 0000096. The functionality would appear as follows: Property: Playlist Condition: is, is not Value: playlist tree with checkboxes This entry should appear after 'Path/Filename' | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?t=5063 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 962 | ||||
|
|
Technical implementation of this feature for Playlists is clear (a simple SQL). For Auto-Playlists it might be a problem, nesting SQL could be hard or impossible. For such cases I'd suggest to execute such nested Auto-Playlist query beforehand, store its result in PlaylistSongs table (which is by default empty for an Auto-Playlist) and then the whole query would be pretty much the same as in case of ordinary Playlist. |
|
|
This issue has been done in build 962 by pre-filling PlaylistSongs table in case of auto-playlists. Now, we are searching for a better solution by merging SQL queries to speed up the process of creating a large auto-playlists. |
|
|
The better solution by merging SQL queries to speed up the process of creating a large auto-playlists has been done in build 962. Note: For more than one selected auto-playlist is slower sometimes, but it seems to be a problem of SQL engine. |
|
|
Fixed Query by Playlist in case of limited AutoPlaylists (used pre-filling of PlaylistSongs table in such cases). i.e. When Auto-Playlist is limited somehow (Show at most: x Tracks, MB, minutes) than pre-filled PlaylistSongs table is used, merged and nested SQL is used otherwise. |
