Bug 1459 - Playlists should be kept in the DB, not the filesystem.
: Playlists should be kept in the DB, not the filesystem.
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Playlists
: 6.0.0
: All All
: P1 major with 1 vote (vote)
: ---
Assigned To: Dan Sully
:
Depends on: 1153
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-28 10:18 UTC by Dan Sully
Modified: 2008-08-18 10:54 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Sully 2005-04-28 10:18:01 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.
Comment 1 KDF 2005-06-16 23:54:57 UTC
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.
Comment 2 Dan Sully 2005-06-24 11:03:43 UTC
This is now merged into the 6.1 branch
Comment 3 Jim McAtee 2006-05-24 17:25:03 UTC
> 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.

Comment 4 Dan Sully 2006-05-24 17:27:44 UTC
Only when the user edits a playlist.
Comment 5 Chris Owens 2008-03-11 11:28:12 UTC
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!