[Digikam-devel] excluding files from database?

[Arnd Baecker]

On Mon, 30 Apr 2007, Gilles Caulier wrote:

> 2007/4/30, Marcel Wiesweg <marcel.wiesweg at gmx.de>:

[...]

> > In the current situation, any file is inserted in the DB, and only when
> > reading from the db, files are filtered by filename.
> > It is of course easy to do the filtering when inserting into the DB.

Yes, that's what I was thinking of.

> > After the
> > initial scanning at startup, new files will be added and files which do no
> > longer belong to the mime type list are removed.

Removed = removed from the database, right?

> > This also solves the problem
> > with wrong album high/low/mean dates.

Oh, that would be very good, indeed!

> > I see one major problem here:
> > A user might by chance or misunderstanding remove e.g. ".jpg" from the
> > mimetype list. Suddely all his photos are gone, which is no problem they
> > can
> > be rescanned. But all tags and ratings are lost!! (unless written to file
> > -
> > assume it is not).

[...]

> > We need to prevent this.
> > One possibility is a hardcoded list of image formats that are supported. I
> > cannot see any indication for removing .jpg from the mime type list.
> > Hm difficult. A positive list of added formats, a negative list? Or keep
> > it as
> > it is, develop another approach?
>
>
> Right Marcel. And this problem is not relevant of JPEG files only. RAW files
> for example can be tagged intensivly. For example i have an huge tagged
> collection of MRW files on my main computer...
>
> Why not to ping users with a confirm dialog when the users change something
> in type mime dialog ?

That sounds like a good solution!
A very very clear warning, if one of the removed files types
is presently in the database, should do the job.

Best, Arnd