[Bug 261277] New: Windows and Linux Frontend using the same database

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=261277

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |2.3.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[julien.t43+kde]

https://bugs.kde.org/show_bug.cgi?id=261277

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #20 from [hidden email] ---
Just as a follow-up of the following thread
http://mail.kde.org/pipermail/digikam-users/2012-September/016862.html
I tried today to share my collections (Linux, external disk, fat32 partition -
recently switched from ext4 to fat32 for sharing as sadly it is still the only
"universal" filesystem recognized by nearly any system) with a macos macbook.

Constraints: because of fat32, I had to move my db files to alternative
locations (instead of Images/) as thumbnails db is far above 2GB as both db
have to stay together. It seems there is no way currently to make it splitted
(by size or by period of time yearly/monthly/...)

Need
* change db path in ~/.kde/share/config/digikamrc or
~/Library/Preferences/KDE/share/config/digikamrc (both Database Name and
Database Name Thumbnails: if the second is different from the first, digikam
will rewrite it with the same previous pah)
* change root path of Images in database. for sqlite
$ sqlite3 ~/path/to/digikam4.db
SQLite version 3.7.14 2012-09-03 15:42:36
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> .headers on
sqlite> select * from AlbumRoots;
id|label|status|type|identifier|specificPath
1|Images|0|1|volumeid:?uuid=1e369250-3d4f-40b3-b65b-7797264c712b|/path1/to/Images
sqlite> UPDATE AlbumRoots SET identifier='volumeid:?path=/new/path2/to/Images',
specificPath='/' WHERE id=1

after I started digikam, rebuild thumbnails and it seems working fine.
Still hope performances will not be too bad with fat32 and not too many
problems in case of crash (fat32 nothing against journaling and else of others)

Other reference
http://comments.gmane.org/gmane.comp.kde.digikam.user/18828
https://bugs.kde.org/show_bug.cgi?id=175923

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=261277

--- Comment #21 from Gilles Caulier <[hidden email]> ---
NTFS 3G is fully support by Linux in RW mode and also under OSX last version or
at least you need to install linux driver adapted for OSX (it's free)

NTFS is journalized and better than FAT 32 about long file naming support...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[julien.t43+kde]

https://bugs.kde.org/show_bug.cgi?id=261277

--- Comment #22 from [hidden email] ---
Sorry but, for most OS, it's "fully supported" with additional drivers.
As currently a traveler, I would say that in many situations, you only rely on
default install and can't/don't want to install applications and especially
drivers.

Linux is the only OS which almost support everything. Most unix rely on
fuse/ntfs-3g and only have native read support (and experimental/not
recommended write). See MacOS, *BSD
http://en.wikipedia.org/wiki/Comparison_of_BSD_operating_systems#Technical_information
http://www.openbsd.org/cgi-bin/man.cgi?query=mount_ntfs
http://forums.macrumors.com/showthread.php?t=1308755
http://en.wikipedia.org/wiki/NTFS#Interoperability

And if additional components are possible, Ext2/3 would be probably a better
choice.
http://en.wikipedia.org/wiki/Ext4#Compatibility_with_Windows_and_Macintosh

For now, I would say that there is a noticeable performance hit using fat32 for
images

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Tex]

https://bugs.kde.org/show_bug.cgi?id=261277

Tex <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #23 from Tex <[hidden email]> ---
I think this is a great but unfortunately probably little known solution (a
front end interface would be nice).  However in real life, it's not very useful
for me because of this related bug:

https://bugs.kde.org/show_bug.cgi?id=302131

It's too bad, because digikam has the potential to be a multiplatform NAS
client to let the whole family (or business) share pictures and tags throughout
the house.  All the real work is done.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=261277

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Multiusers

--
You are receiving this mail because:
You are the assignee for the bug.