gSoC Implement a better database schema

[Ben K]

Fixing that bug doesn't require a schema change; you just write nulls
instead of zeros and change the handling of the two values.

The Amarok devs spent quite a lot of time coming up with new schema used in
Amarok 2, and I suspect they'll be reluctant to change it. There were also
quite specific reasons for moving to MySQLe and only MySQL backend - it
means far lower support costs than when you have potentially 3 different
backends (you don't have to manage three sets of interfaces).

I like your suggested behaviour for ratings, and null seems to me to be the
way to represent unrated, given that null means 'no information', but I
don't think this is an entire GSoC project. You could probably fix 172112 in
a few days of coding. Why don't you give it a shot and submit a patch to the
bug?

On Thu, Mar 26, 2009 at 8:58 AM, Caleb Cushing <xenoterracide at gmail.com>wrote:

> Most of what I want to do is fix this bug
> https://bugs.kde.org/show_bug.cgi?id=172112 but as long as I'm up to
> correcting things like proper handling of nulls, I might as well
> correct the rest of the way the database works (quite a few
> denormalized things in it). While working on it I hope also to make
> the format portable enough to support other databases, such as
> postgres. The only user interface change that I can see (that's not
> planned) is the ability to specify ratings of 0, I would suggest
> making the stars have 3 clicks, 1 full start, 2, half, 3 no star.
>
> questions, comments, suggestions welcome.
> --
> Caleb Cushing
>
> http://xenoterracide.blogspot.com
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20090326/1a070049/attachment.html>