gSoC Implement a better database schema

[Caleb Cushing]

On Wed, Mar 25, 2009 at 7:03 PM, Ben K <mrmrpotatohead at gmail.com> wrote:
> 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?

Sometimes, when people say this:

    The source code is freely available. If you feel so strongly about
this bugfix/tweak/feature/plugin, why don't you code it yourself?

They're really saying this:

    F**k you.

- Jeff Attwood

http://www.codinghorror.com/blog/archives/001247.html given that's not
the whole point of the blog post, but it seems to fit right.

-- 
Caleb Cushing

http://xenoterracide.blogspot.com