[mythtv] sql code

[Matthew S. Hallacy]

On Thu, Feb 20, 2003 at 01:04:36PM -0500, Andy Davidoff wrote:

> I think we probably want default playlists per front-end.  If you agree, then
> the quickest way to implement this is to pick a setting variable in which to
> store the playlistid.  It'll default to 1 for hostname = NULL and your UI can
> update the setting entry for the front-end host when it wants to change the
> default for that node.

> 
> If you've already made playlist objects, send them to me and I'll patch them
> to do incremental saves.  This will let us update the playlist in real-time
> as it's changed by the user, which means we don't need to save the playlist
> at shutdown and the cost of updates becomes O(n) versus O(n)+length(list).
> 
> At the moment I'm trying to make sense of why it does a selection for each
> and every playlist entry.  I only have one album in my database, and it
> still takes a couple seconds to load the "Select Music" dialog.   Fixing
> the hierarchial selection widget should make that pretty much instant.

How about a master playlist that is always used, it could contain other
playlists (as opposed to playlists only containing songs/tracks/etc).

-- 
Matthew S. Hallacy                            FUBAR, LART, BOFH Certified
http://www.poptix.net                           GPG public key 0x01938203