SQL backend consolidation

[Seb Ruiz]

On 16/08/07, Ian Monroe <ian at monroe.nu> wrote:
> Markey and I were talking about how we should perhaps drop Postgresql
> and Sqlite, and just use MySQL embedded (in-process mysql support) and
> perhaps support external MySQL as well.
>
> The primary advantage would be we'd have less to support. Just MySQL.
> Supporting sqlite, mysql and postgresql has been a real burden. The
> secondary advantage is the MySQL 5 is almost a real database and it
> has a lot of features we could take advantage of. Views, probably more
> consistency checking. Currently we are held back by the limited subset
> of SQL that sqlite supports. Also recent versions of sqlite have been
> having corruption fixes.

I think postgres support is a really awesome thing to have, and I know
of many people that use it. What is the advantage to dropping it,
aside from the obvious cop out that it is less to maintain?

Postgresql is more robust than Mysql, and requires virtually the same
syntax (except for some more complicated statements). I'd be happy to
keep postgres up to date.

Also, did we come to a conclusion on the QtSql packages?

Seb

>
> What do folks think?
> Ian
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>


-- 
http://www.sebruiz.net/