On 10/11/07, Jeff Mitchell <kde-dev@emailgoeshere.com> wrote:
> On Saturday 06 October 2007, Ian Monroe wrote:
> > *what you'd really want to migrate and backup is in the MySQL,
> > PostgreSQL or sqlite database in the statistics table. Thanks to file
> > tracking we don't have to worry about if the users put the file in a
> > different location really on different computers.
>
> Speaking of file tracking, that'll have to get sorted at some point for 2.0.
> It'll have to be totally rewritten, considering the original implementation
> was heavily integrated into MetaBundle and CollectionDB  :-)  ...except for
> the basic algorithm (which is the hard part anyways, really).  Just another
> thing to tick up on our TODO list.

Would it make sense to use musicbrainz UUID here to identify tracks
rather than our own method?  It seems like musicbrainz UUID is become
a commonly used method of identifying a unique track, xspf supports
it, xesam supports it, and I think some forms of metadata support it.
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel@kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel