use case scenario of Meta::Playlist, including Dynamic

[Jeff Mitchell]

Bart Cerneels wrote:
> facts: Playlists should be saved to SQL and abstraction if good.

This brings up an interesting question: although "new" playlists the 
user creates should be stored in SQL and exported on request to (M3U, 
XSPF, PLS, whatever), what about playlists found during a scan, or found 
during a Xesam query?  Do those get imported into internal SQL 
playlists?  If so, what happens when they are modified...does it do an 
automatic export, or leave the original playlist alone, or...?  (I think 
automatic export makes sense, but users are always prone to being upset 
when anything is automatically touched.)

I definitely think playlists should be SQL but this case has to be handled.

--Jeff