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.

as I recall on a previous occasion I was told that it would require
more than that because there are lots of things expecting 0's instead
of nulls.

> 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.

I must have missed this one too?

> 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'm aware, but there are some of us who want to see (better) support
for pg. I think we can live without sqlite (although all this FPIC
stuff is more annoying to distro's)

> 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?
>

well you might be right, it's entirely possible that the complexity of
this issue has been previously exaggerated to me. tbh, I've no idea
what it would take, I've looked at the schema, it'd be a couple of
days to rewrite that, but none of the C++. it's kind of a priority
thing, and then I thought, maybe I could wrap all this stuff into one
gsoc project.
-- 
Caleb Cushing

http://xenoterracide.blogspot.com