Multi-user with mysql server

[stancs3]

Hi Folks,

I have DigiKam set up with a remote mysql server, with about 28K
images. So far it has operated perfectly. I have made a pretty typical
set of mistakes, and DigiKam has has no trouble. This is in stark
contrast with competing apps, where crashes are regular, even during
test runs with few images.

So, this is looking like a tremedous app. I had past questions here
regarding the risk of using mysql server, but I took the plunge.

I have a couple of operational questions regarding multi user
techniques.

Let's say I have the following:

- pc1 working as described, connected to mysql_server_1.

- The images are maintained such that I have a duplicate and synced
copy on pc2.

- pc2 also connects to mysql_server1, I guess as a different user .....


What is the expected reaction of DigiKam?:

>> If I modify metadata using pc2 such that mysql_server_1 becomes
changed from the last time pc1 did something to it.

>> Then use pc1 again, which is still connected to mysql_server_1.

>> I could just try it, but at this point I now have so much invested
in set up that I don't want to corrupt things. (Yes, this calls for a
separate test bed, which I plan to do .... .

This describes a potential user case scenario where I generally
administer the whole thing on pc1, and sometimes my wife uses her pc2
to do some ranking etc. I do not expect pc2 to do actual image changes,
but if so, it is my job to keep the images in sync between pc1 and pc2,
a backend task.

Thanks again!

Stan

[stancs3]

The following seemed to disappear - resend.

-------- Forwarded Message --------
From: stancs3 <[hidden email]>
To: [hidden email] <[hidden email]>
Subject: Multi-user with mysql server
Date: Wed, 25 Jan 2017 12:47:31 -0700

Hi Folks,

I have DigiKam set up with a remote mysql server, with about 28K
images. So far it has operated perfectly. I have made a pretty typical
set of mistakes, and DigiKam has has no trouble. This is in stark
contrast with competing apps, where crashes are regular, even during
test runs with few images.

So, this is looking like a tremedous app. I had past questions here
regarding the risk of using mysql server, but I took the plunge.

I have a couple of operational questions regarding multi user
techniques.

Let's say I have the following:

- pc1 working as described, connected to mysql_server_1.

- The images are maintained such that I have a duplicate and synced
copy on pc2.

- pc2 also connects to mysql_server1, I guess as a different user .....


What is the expected reaction of DigiKam?:

>
> >
> > If I modify metadata using pc2 such that mysql_server_1 becomes
changed from the last time pc1 did something to it.

>
> >
> > Then use pc1 again, which is still connected to mysql_server_1.
>
> >
> > I could just try it, but at this point I now have so much invested
in set up that I don't want to corrupt things. (Yes, this calls for a
separate test bed, which I plan to do .... .

This describes a potential user case scenario where I generally
administer the whole thing on pc1, and sometimes my wife uses her pc2
to do some ranking etc. I do not expect pc2 to do actual image changes,
but if so, it is my job to keep the images in sync between pc1 and pc2,
a backend task.

Thanks again!

Stan

[Gilles Caulier-4]

Hi,

These scenario cases are not yet well managed by datbase interface, especially the concurrency queries to the data.

Look in bugzilla, there is a specific section to group all wishes about this topic :

https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Database-Multiusers&list_id=1419270&product=digikam&query_format=advanced

Best

Gilles Caulier

2017-01-31 23:56 GMT+01:00 stancs3 <[hidden email]>:

The following seemed to disappear - resend.

-------- Forwarded Message --------
From: stancs3 <[hidden email]>
To: [hidden email] <[hidden email]>
Subject: Multi-user with mysql server
Date: Wed, 25 Jan 2017 12:47:31 -0700

Hi Folks,

I have DigiKam set up with a remote mysql server, with about 28K
images. So far it has operated perfectly. I have made a pretty typical
set of mistakes, and DigiKam has has no trouble. This is in stark
contrast with competing apps, where crashes are regular, even during
test runs with few images.

So, this is looking like a tremedous app. I had past questions here
regarding the risk of using mysql server, but I took the plunge.

I have a couple of operational questions regarding multi user
techniques.

Let's say I have the following:

- pc1 working as described, connected to mysql_server_1.

- The images are maintained such that I have a duplicate and synced
copy on pc2.

- pc2 also connects to mysql_server1, I guess as a different user .....


What is the expected reaction of DigiKam?:

>
> >
> > If I modify metadata using pc2 such that mysql_server_1 becomes
changed from the last time pc1 did something to it.

>
> >
> > Then use pc1 again, which is still connected to mysql_server_1.
>
> >
> > I could just try it, but at this point I now have so much invested
in set up that I don't want to corrupt things. (Yes, this calls for a
separate test bed, which I plan to do .... .

This describes a potential user case scenario where I generally
administer the whole thing on pc1, and sometimes my wife uses her pc2
to do some ranking etc. I do not expect pc2 to do actual image changes,
but if so, it is my job to keep the images in sync between pc1 and pc2,
a backend task.

Thanks again!

Stan