[mythtv] sql code

[thor]

On Thursday 20 February 2003 01:26 pm, Isaac Richards wrote:

> I don't want any table creation/deletion going on in the program.  I do not
> want to deal with multiple upgrade paths at this point in development.

	OK, I won't commit anything as it stands. If Andy can moce the changes into a 
SQL script and then have the code assume the new structure is in place, is 
that ok?

>
> Now, considering it takes less than a tenth of a second to load a playlist
> containing my entire music collection with the current code on my machine,
> is this necessary?  Playlist loading/saving _rarely_ happens, so this is
> more of a complication than an optimization.
>

	It's clearly far from mission critical, but it may well be useful. As I've 
been struggling (given my ineptitude with Qt) to design (and redesign ... and 
redesign) a simple playlist editor, it's become apparent that having the 
playlist changes happen quickly will be useful (select a playlist from a one 
line Combo box, have those changes immediately reflected in a Listview on the 
same page). Could hold all the playlists in memory and only update when 
leaving the dialogue, but it would be nicer to make a screen click persist 
directly to the DB in an efficient way.

- thor