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

[Mark Kretschmann]

On Sun, Aug 30, 2009 at 4:47 AM, Seb Ruiz<ruiz at kde.org> wrote:
> 2009/8/30 Ian Monroe <ian.monroe at gmail.com>:
>> On Sat, Aug 29, 2009 at 7:35 PM, Seb Ruiz<ruiz at kde.org> wrote:
>>> 2009/8/30 Leo Franchi <lfranchi at kde.org>:
>>>> There are no plans for anything other than msyql support. In fact, it was a
>>>> conscious decision to standardize on 1 database to make our life easier and to
>>>> make the user experience better. We're not SQL experts, so it makes our head
>>>> hurt to have to manage multiple.
>>>>
>>>> That said, just calling it "Database backend" could be misleading because it
>>>> has to be a MySql database for it to work. I would vote for no combobox, b ut
>>>> it has to be clear that it is Mysql.
>>>>
>>>
>>> That said, if we can provide an adequate unit testing environment, we
>>> should be able to create database tests to avoid regressions like we
>>> had with 1.4. I'd love psql support.
>>
>> ...why?
>
> Because when you use postgres, you realise that it is the database
> that mysql should have been. For example: it is fast, it's robust,
> extensible, and it doesn't do stupid things like truncate long text
> fields silently.

While I'm not completely happy with the way MySQL is heading
(politically, technically, packaging wise), please let's not go back
to the terrors of supporting multiple database engines.

I'd much rather stick with one database. If we find a better solution
than MySQL, by all means, let's switch over completely.

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org