Bugzilla – Bug 1459
Playlists should be kept in the DB, not the filesystem.
Last modified: 2008-08-18 10:54:16 UTC
I'm working on a patch - this should speed things up dramatically, especially for now playing. Periodically, the playlists should be flushed to disk, so a DB being removed won't nuke the playlists. That should be in concert with bug 1153.
I tried the recent patch submitted to the dev list. on startup, I would get some odd error messages showing the song name but I've since backed out. If you have not moved beyond that last patch I can always try it out again and give more detail. it also seemed to leave my current playlists blank on restart if that current playlist was created by the random plugin.
This is now merged into the 6.1 branch
> Periodically, the playlists should be flushed to disk, so a DB being removed > won't nuke the playlists. When is this flushing done? Seems it should only be done when a user is creating or modifying a playlist, rather than "periodically". I'm thinking of the instance where someone modifies a playlist outside of SlimServer. If SlimServer decides to "refresh" the playlist file from whatever it has in the db, then those changes would be lost.
Only when the user edits a playlist.
This bug was marked resolved in Slimserver 6.1, which is several versions ago. If you're still seeing this bug, please re-open it. Thanks!