Review of Digikam

[Gilles Caulier-2]

Le jeudi 21 décembre 2006 20:01, Gonçalo Valverde a écrit :
> GIMP is a lot easier and more fun to use.

Really !!!

Gimp GUI is a shame.

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

[Gerhard Kulzer]

Am Samstag, 16. Dezember 2006 15:08 schrieb jdd:

> Duncan Hill a écrit :
> > There are tools for doing backups that do them very well.
>
> the problem is backing up the data base in the way they
> don't lose track of images. this is very difficult to acheive.
>
> > The benefit of the sqlite database file is that you have on central
> > location to easily store and retrieve the information.
>
> and the need of yet another database engine...
>
>    This also makes
>
> > it faster than scanning 8000 photos to find all photos matching
> > 'london'.
>
> there is no "london" in any photo if you don't key it in
> yourself
>
> I use digikam for more than a year now and have already lost
> my datas 2 or three time :-((

How did you do that?
I use digiKam since 3 years now, I compile daily from svn (riskier it cannot
come, I had many, many crashes), I've about 18000 images tagged and I never
lost any tags. In my opinion the most stable thing in digikam is sqlite and
therefore tagging.

Gerhard

> tagging and commenting the images is extremely tedious and
> making this more than once is more than I can support :-(
>
> jdd

--
http://www.gerhard.fr
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Oliver Dörr]

Gerhard Kulzer wrote:

Am Samstag, 16. Dezember 2006 15:08 schrieb jdd:
  

Duncan Hill a écrit :
    

There are tools for doing backups that do them very well.
      

the problem is backing up the data base in the way they
don't lose track of images. this is very difficult to acheive.

    

The benefit of the sqlite database file is that you have on central
location to easily store and retrieve the information.
      

and the need of yet another database engine...

   This also makes

    

it faster than scanning 8000 photos to find all photos matching
'london'.
      

there is no "london" in any photo if you don't key it in
yourself

I use digikam for more than a year now and have already lost
my datas 2 or three time :-((
    

How did you do that? 
I use digiKam since 3 years now, I compile daily from svn (riskier it cannot 
come, I had many, many crashes), I've about 18000 images tagged and I never 
lost any tags. In my opinion the most stable thing in digikam is sqlite and 
therefore tagging.
  

Sorry,

but i lost my tags also two times and so i given up tagging my images. I don't know how it happened, perhaps it has something to do with not exactly knowing how tagging works technically and doing something wrong on my own.

-> Loosing tags is a serious problem, because it destroys so much work and this destroys trust into this feature.

Sorry
Oliver

PS: I'm managing 13841 photos with digikam.
PPS: I personally don't believe that sqlite is stable, at least not the way i'm using it. Me and my wife are using on computer with digikam and the same album library path. So from to time digikam is started twice. I now the digikam is not designed for that, but thats we way the us it ;-)

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

Gerhard Kulzer a écrit :

> How did you do that?
> I use digiKam since 3 years now, I compile daily from svn (riskier it cannot
> come, I had many, many crashes), I've about 18000 images tagged and I never
> lost any tags. In my opinion the most stable thing in digikam is sqlite and
> therefore tagging.

there are many situations.

the easiest to reproduce is the fact that I have not the
disk room to have all my photos on line, I need to stroe
them on dvd. How do I store the database?

My photo collection was growing, I had to move it to an
other disk, bigger, guess what? data base lost.

not to mention several others ways I don't remember the
details (and the fact that the comments are -where?- not
utf8 stable).

jdd


--
http://www.dodin.net
http://dodin.org/mediawiki/index.php/GPS_Lowrance_GO
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Duncan Hill-5]

On Thursday 21 December 2006 20:27, Oliver Dörr wrote:

> PPS: I personally don't believe that sqlite is stable, at least not the
> way i'm using it. Me and my wife are using on computer with digikam and
> the same album library path. So from to time digikam is started twice. I
> now the digikam is not designed for that, but thats we way the us it ;-)

I forget where I read it, but SQLite does NOT support concurrent access to the
same datafile due to the way it operates.  If you're using a tool in a manner
that isn't supported by the tool, then you should expect problems to happen -
it's like using a 50 lb hammer to adjust your watch.  

I'd almost say that digiKam should execute an exclusive file lock on the
database when it boots up, and pray that your concurrent access method passes
on the exclusive lock information.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Markus Spring]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan Hill schrieb:

> On Thursday 21 December 2006 20:27, Oliver Dörr wrote:
>
>> PPS: I personally don't believe that sqlite is stable, at least not the
>> way i'm using it. Me and my wife are using on computer with digikam and
>> the same album library path. So from to time digikam is started twice. I
>> now the digikam is not designed for that, but thats we way the us it ;-)
>
> I forget where I read it, but SQLite does NOT support concurrent access to the
> same datafile due to the way it operates.  If you're using a tool in a manner
> that isn't supported by the tool, then you should expect problems to happen -
> it's like using a 50 lb hammer to adjust your watch.  
>
> I'd almost say that digiKam should execute an exclusive file lock on the
> database when it boots up, and pray that your concurrent access method passes
> on the exclusive lock information.

in fact, it does lock the database for other applications. I use a perl script
to sophistically rename my image files and database entries, and this script
stops when digikam is open - at least when already a write operation had be
performed on the database.
Probably the application should prevent another instance to be started on the
same database.

Regards - Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFi7H7xxUzQSse11ARAmenAJ0RRoPZ87WzhQem9yqA8Li1M4SkLACfZ2bN
xGXpBsqVaWANy3i4o5qB8XA=
=WoJH
-----END PGP SIGNATURE-----
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Oliver Dörr]

Duncan Hill wrote:

On Thursday 21 December 2006 20:27, Oliver Dörr wrote:

  

PPS: I personally don't believe that sqlite is stable, at least not the
way i'm using it. Me and my wife are using on computer with digikam and
the same album library path. So from to time digikam is started twice. I
now the digikam is not designed for that, but thats we way the us it ;-)
    

I forget where I read it, but SQLite does NOT support concurrent access to the 
same datafile due to the way it operates.  If you're using a tool in a manner 
that isn't supported by the tool, then you should expect problems to happen - 
it's like using a 50 lb hammer to adjust your watch.  
  

I know that i'm not using digiKam the way it is designed for. I use it the way i need :-D

As a conclusion, i don't use the features like tags, because they are *not* reliable. However digiKam is the best application that i know for my personal needs.

The only reason i wrote my mail was that Gerhard thinks that the tagging feature is very reliable. In fact this depends on how use digiKam.

Oliver

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