proposed solution for defects 90095 & 119539 (674 votes, 638 votes) (Multiple artists per song)

[Ian Monroe]

On Sat, Aug 30, 2008 at 2:40 PM, Lydia Pintscher
<lydia.pintscher at gmail.com> wrote:
> On Sat, Aug 30, 2008 at 20:56, Mark Kretschmann <kretschmann at kde.org> wrote:
>> On 8/30/08, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
>>>  One other note:  I think for A2 we should make a habit of creating a copy of
>>>  the user's collection file -- easy if it's embedded, i.e. sqlite or mysqle --
>>>  every time we run the database updating function.  If we cannot make that
>>>  copy, we should not continue with the upgrade; also, this way, if a user says
>>>  that the upgrade toasted their collection, they'll have a backup to work from
>>>  to try to figure out what's going wrong.
>>
>> This sounds like a really good idea to me :)
>
>
> Yes it does :)
>
> What about the db versioning people were talking about? Do we still
> want it? If so we should probably take care of it now.

Our DB already has a version.

It would be nice to implement a quassel-like system of database
updating (where the sql is loaded from external files); maybe thats
what you meant. But its a bit late for that now, and it could be
implement later.

Ian