State of the MySQL support

[Gilles Caulier]

2017-08-09 21:27 GMT+02:00 Mario Frank <mafrank at uni-potsdam.de>:
> Hey Guys and Ladies,
>
> as you probably have seen the current problem with moving tags in the
> hierarchy making
> the DB corrupt, I would like to address this in a broader way.
>
> I am aware that the MySQL support is experimental (for a quite long time).
> But I also experience that users complaining about problems in
> combination with MySQL
> becomes more frequent. The long-established devs of you may have other
> experiences,
> so correct me if my experience is due to my quite short time in the
> digiKam world.
>
> As I am trying to fix the current problem, this is no overall solution
> to the experimental state.
>
> So, what I like to address is the following:
> 1) Do we have some "specialists" in MySQL in our ranks? I am no
> specialist here, I am more experienced in postgres.

Richard Mortimer <richm at oldelvet dot org dot uk>, normally in this
room is the expert in Mysql. He has already posted a lots of patches
to improve DB backend stability and schema. He also guide Swati while
summer 2016.

> 2) Could we determine how many users are affected by such problems, i.e.
> what is the ratio of MySQL users?

Good question. The only way is to check bugzilla. As i reroute all
reports by sub-categories, it can be more easy. There is a
database-mysql component in bugzilla.

> 3) What are the plans for MySQL support?

To improve and finalize. This is important especialy to have a network
backend with multi-users supports (as multi-digiKam clients running on
different computer / OS). This is the typical use case in photo
agency.

> 4) Is further support for other DBMS desirable (I think of postgres)?

There is an entry in bugzilla to add postgressql support. The low
level must be easy as a Qt plugin exist. The most complicated is to
write a schema compatible with this kind of DB. We need another expert
here.

Gilles