[Digikam-devel] What do we want to store in the database?

[Gilles Caulier]

2007/8/30, Julien Narboux <Julien.Narboux at inria.fr>:
>
>
> > ((To me this example just highlights that it would be nice
> > to allow for easy additions of new fields in the
> > database in the future, i.e. withouth the need to wait for
> > a 0.9 to 0.10 transition ...))
> >
> I think you are raising the right question. I am not a specialist of
> databases.
> Currently, It seems to me that changing the database format is something
> the developpers do not want to do too often and they rather want to wait
> for major releases.
> That is why I proposed some field which may be useful only in a far
> future. I understand as Gilles said that some fields are currently hard
> to extract because in Makernote. But maybe one day these fields will be
> in new version of the exif standard...


I have never said than i won't to store few Makernotes info in DB. I just
want to define the priority.

In first all info witch are easy to extract must be store. Others can be
done later, because it's require more devel. time, especially about to parse
all Makernotes cases.

About a future Exif 3.0 version, this sound like a vaporware. try to find
Exif 3.0 information with Google, you will be surprised.

Of course, i'm agree with you than Exif spec must be improved, but this is
not a simple task. Currently all makers use makernotes area to store
unsupported tags by Exif 2.2. Perhaps than camera makers stand a new format
to store data, for ex. XMP (:=))) But i'm not sure...


Should these fields already be on the database right now even if they
> are not filled  by Digikam and the corresponding features are not yet
> implemented ?


Yes, it's possible. Marcel your viewpoint ?

Gilles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20070830/846f0dde/attachment.html>