start of new DB design

[Ian Monroe]

On 6/6/07, Maximilian Kossick <mkossick at gmx.de> wrote:
> And another idea: you could remove the distinction between trackid and
> externalid in the table if you'd just store the urls (as returned by
> Track::url(). The method is designed for cases like this. ) in the table.
> That way we could easily handle multiple SQL collections (i'm not sure if we
> want to add this functionality) and it would make the code a lot easier.
> As pseudo-code:
>
> load all urls from the current playlist table
> for each url
> {
>         call CollectionManager:::trackForUrl
>         if result of trackForUrl != 0
>                 insert track into playlist
>         else
>                 create and insert proxy
> }

I'm worried that this wouldn't be fast enough. Currently in the XML
file we store all the metadata information, so it doesn't have to read
any tags to load the playlist. Its important that the playlist loads
fast since its part of the initial application load time.

This would certainly be a lot easier though.

Ian