digiKam › digikam-users

mysql - 5.3

classic Classic list List threaded Threaded
♦
♦
 4 messages Options
stancs3
Reply | Threaded
Open this post in threaded view
♦
♦
|

mysql - 5.3

stancs3
Just starting out with digiKam and attempting to get the db in place.

The 5.0.0 release info was informative re mysql development. I cannot
find anything else beyond this.

mysql shows experimental in 5.3.0 that I have running.

My options:

1. start with sqlite, then migrate to mysql/maria at the right time.

2. start with mysql/maria now.


My collection is getting close to 100K and I have experience with
mysql/maria and prefer postgresql actually. I have replicated postgres
servers running backends for other apps.


Any pointers would be very much appreciated. I am really looking
forward to working with digKam. Migrating from Lr5; another Win app to
leave behind :).


Stan
Gilles Caulier-4
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: mysql - 5.3

Gilles Caulier-4
Hi,

Start to read the documentation here :


...and ask your questions in second stage...

Best

Gilles Caulier

2017-01-08 22:29 GMT+01:00 stancs3 <[hidden email]>:
Just starting out with digiKam and attempting to get the db in place.

The 5.0.0 release info was informative re mysql development. I cannot
find anything else beyond this.

mysql shows experimental in 5.3.0 that I have running.

My options:

1. start with sqlite, then migrate to mysql/maria at the right time.

2. start with mysql/maria now.


My collection is getting close to 100K and I have experience with
mysql/maria and prefer postgresql actually. I have replicated postgres
servers running backends for other apps.


Any pointers would be very much appreciated. I am really looking
forward to working with digKam. Migrating from Lr5; another Win app to
leave behind :).


Stan
stancs3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: mysql - 5.3

stancs3
Hi Gilles,

Many thanks for the quick reply. I had read that documentation, and I re-read it to be sure.
It is good that the instructions indicate easily how to setup for mysql/mariadb.

I am very likely to proceed with mysql/mariadb, but I am a bit concerned that it is at the 'experimental' stage. Usually I don't have a problem with being leading edge.

So, I am looking for a little advice on whether it is better to use sqlite right now, and wait for the mysql to mature a bit more. Or, whether mysql is stable enough now, and it is simply small improvements yet to come.

I cannot judge this myself unless I try out both; which is of course OK too.


Stan


On Sun, 2017-01-08 at 23:20 +0100, Gilles Caulier wrote:
Hi,

Start to read the documentation here :


...and ask your questions in second stage...

Best

Gilles Caulier

2017-01-08 22:29 GMT+01:00 stancs3 <[hidden email]>:
Just starting out with digiKam and attempting to get the db in place.

The 5.0.0 release info was informative re mysql development. I cannot
find anything else beyond this.

mysql shows experimental in 5.3.0 that I have running.

My options:

1. start with sqlite, then migrate to mysql/maria at the right time.

2. start with mysql/maria now.


My collection is getting close to 100K and I have experience with
mysql/maria and prefer postgresql actually. I have replicated postgres
servers running backends for other apps.


Any pointers would be very much appreciated. I am really looking
forward to working with digKam. Migrating from Lr5; another Win app to
leave behind :).


Stan
Gilles Caulier-4
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: mysql - 5.3

Gilles Caulier-4


2017-01-09 1:33 GMT+01:00 stancs3 <[hidden email]>:
Hi Gilles,

Many thanks for the quick reply. I had read that documentation, and I re-read it to be sure.
It is good that the instructions indicate easily how to setup for mysql/mariadb.

I am very likely to proceed with mysql/mariadb, but I am a bit concerned that it is at the 'experimental' stage. Usually I don't have a problem with being leading edge.

So, I am looking for a little advice on whether it is better to use sqlite right now, and wait for the mysql to mature a bit more. Or, whether mysql is stable enough now, and it is simply small improvements yet to come.

The Mysql interface is more mature than before. A lots of bugs have been fixed.

For the 3 DB interfaces that we use in DK i can said :

- Sqlite : very mature and stable, but problematic with large collection (100K items start to introduce time latency).
- Mysql internal : to replace sqlite in local (no network). Work better for large collections. It can still few bugs.
- Mysql : remote DB through the network (can be in local too). As last one, but network can introduce time latency with huge albums contents. It's not yet optimized.

The migration tool still problematic too. take a care.

I recommend to parse all reports from bugzilla about *database* sections, to have a clear vision.


Best

Gilles Caulier
 

I cannot judge this myself unless I try out both; which is of course OK too.


Stan


On Sun, 2017-01-08 at 23:20 +0100, Gilles Caulier wrote:
Hi,

Start to read the documentation here :


...and ask your questions in second stage...

Best

Gilles Caulier

2017-01-08 22:29 GMT+01:00 stancs3 <[hidden email]>:
Just starting out with digiKam and attempting to get the db in place.

The 5.0.0 release info was informative re mysql development. I cannot
find anything else beyond this.

mysql shows experimental in 5.3.0 that I have running.

My options:

1. start with sqlite, then migrate to mysql/maria at the right time.

2. start with mysql/maria now.


My collection is getting close to 100K and I have experience with
mysql/maria and prefer postgresql actually. I have replicated postgres
servers running backends for other apps.


Any pointers would be very much appreciated. I am really looking
forward to working with digKam. Migrating from Lr5; another Win app to
leave behind :).


Stan
Free forum by Nabble Edit this page