Windows and Linux Frontend using the same database

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Windows and Linux Frontend using the same database

Bugzilla from tobias@kaminsky.me
Hello,

I have one database and three frontends. Frontend#2 is on Windows.
Therefore I have two entries in AlbumRoots:
4 fotos 0 3 networkshareid:?mountpath=%2Fmnt%2Fraid%2Ffotos /
5 fotos 0 3 networkshareid:?mountpath=Y:%2F /

All albums are now stored twice:
372     4     /unsortiert/Neuer Ordner     2010-07-11     NULL     NULL
    NULL
605     5     /unsortiert/Neuer Ordner     2010-07-11     NULL     NULL
    NULL

As you can see 4/5 is the AlbumRoots.id.
The problem is that, if I add a tag to one image on Windows the image is
related to album.id=605.
Linux does not recognize the tag as the same image is stored in
album.id=372.

The solution would be a "meta"-album which contains both albumRoots so
one image is always in the same album.
This would look something like this:

Image=300 --> Meta-Album=1
Meta-Album=1 --> AlbumRoots=1 AND AlbumRoots=2 (1:n relation)
Album-Roots=1: Linux: /mnt/raid/fotos
Album-Roots=2: Win: Y:\

Additional there must be a test if digikam should use Album-Roots=1 or
Album-Roots=2.

Or is there some built-in feature that I have missed?

Thank you for your great app!
Tobias Kaminsky
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Windows and Linux Frontend using the same database

Marcel Wiesweg

> I have one database and three frontends. Frontend#2 is on Windows.
> Therefore I have two entries in AlbumRoots:
> 4 fotos 0 3 networkshareid:?mountpath=%2Fmnt%2Fraid%2Ffotos /
> 5 fotos 0 3 networkshareid:?mountpath=Y:%2F /

The solution would be to have a common identifier for the network share on
Windows and Linux. After all, it's the same directory. But there is no such
solution implemented at the moment. I'm not a Windows developer. On Unix it
would be easy to adjust mount paths, but on Windows there's probably a
problem.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Windows and Linux Frontend using the same database

Bugzilla from tobias@kaminsky.me
I would like to help you to find a solution, but I am not a developer.
I could only test a patch or something like that.

Maybe one should use the album label, in my case "fotos", as a common
identifier.
Then it would be possible to have multiple paths for the same folder.
An album would have "fotos" as "AlbumRoot".

I do not know if this works, but it would be great to have this feature.

Thank you!
Tobias Kaminsky

On 19/12/10 16:10, Marcel Wiesweg wrote:

>> I have one database and three frontends. Frontend#2 is on Windows.
>> Therefore I have two entries in AlbumRoots:
>> 4 fotos 0 3 networkshareid:?mountpath=%2Fmnt%2Fraid%2Ffotos /
>> 5 fotos 0 3 networkshareid:?mountpath=Y:%2F /
> The solution would be to have a common identifier for the network share on
> Windows and Linux. After all, it's the same directory. But there is no such
> solution implemented at the moment. I'm not a Windows developer. On Unix it
> would be easy to adjust mount paths, but on Windows there's probably a
> problem.
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Windows and Linux Frontend using the same database

Vlado Plaga
Am Sun, 19 Dec 2010 21:24:24 +0100
schrieb Tobias Kaminsky <[hidden email]>:

> > The solution would be to have a common identifier for the network
> > share on Windows and Linux.

So using the same database on Windows and Linux works for you? I had
some problems using the same database on Mac OS and Linux, although
paths are no problem on these Unix-like systems.

Now I'm waiting for digiKam 2.0 with XMP sidecars, which should make it
possible to share pictures on different systems no matter what paths or
databases they use... that should also fix your problem.

Vlado

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

signature.asc (197 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Windows and Linux Frontend using the same database

Marcel Wiesweg
In reply to this post by Bugzilla from tobias@kaminsky.me

> Maybe one should use the album label, in my case "fotos", as a common
> identifier.
> Then it would be possible to have multiple paths for the same folder.
> An album would have "fotos" as "AlbumRoot".

It would be possible to add a hack, like allowing an alternative mount path
for a network share. I'll see to find time for this.
It seems impossible atm to have a clean out-of-the-box solution, like with
partition UUIDs for removable media.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Windows and Linux Frontend using the same database

Bugzilla from tobias@kaminsky.me
That would be great.
If you write a patch I could apply it. Using svn, testing it, etc. is
not the problem. Unfortunaly I cannot write real, good code...

Thank you
Tobias

On 20/12/10 23:10, Marcel Wiesweg wrote:

>> Maybe one should use the album label, in my case "fotos", as a common
>> identifier.
>> Then it would be possible to have multiple paths for the same folder.
>> An album would have "fotos" as "AlbumRoot".
> It would be possible to add a hack, like allowing an alternative mount path
> for a network share. I'll see to find time for this.
> It seems impossible atm to have a clean out-of-the-box solution, like with
> partition UUIDs for removable media.
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel