Multiple Databases [WAS: Re: Junior Job - external MySQL config]

[Ian Monroe]

On Sun, Aug 30, 2009 at 3:57 AM, Modestas Vainius<modestas at vainius.eu> wrote:
> Hello,
>
> On sekmadienis 30 Rugpjūtis 2009 11:28:43 Seb Ruiz wrote:
>> 2009/8/30 Modestas Vainius <modestas at vainius.eu>:
>> > You are forgetting that people might already have a database server in
>> > place. Since MySQL and PostgreSQL are both free software, not supporting
>> > them both "by design" will make some people unhappy (esp. since it a
>> > feature regression from 1.4). People won't switch database servers for
>> > Amarok and it is more likely they will dump Amarok. On the other hand,
>> > you don't have to implement something you are not interested in, just
>> > don't close the doors for somebody to come and do it.
>>
>> This argument leads to a giant black hole: it does not have to be
>> implemented because it's free, and a patch does not have to be
>> accepted because it has been provided. At the end of the day we need
>> to make a decision which is "for the betterment of the project" - even
>> if that means rejecting great code because it is clear that it will
>> become bitrotted due to lack of maintainership. (This is not directly
>> related to the multidb argument, btw)
>
> I don't see how getting tied to one database solution will make your life
> easier to switch when "a better solution arrives".

We add the new db, drop the old DB. Its not so difficult to understand.

And regardless its all going to be 100% configuration free, 95% of
users won't even know they are running a database, and less will know
which kind of database.

Ian