Am 10.11.2012 17:39, schrieb Michael Born: > The problem could be reproduced with the rolled-back version of DT. > Starting without library.db and mipmap. Importing one folder. "mark all" > and "remove". Then trying to import the folder again failed without an > error message. > > Doing the same with the current git build - re-importing worked. > > So, my library.db was broken by a former DT version. With a fresh > library.db and the current git DT version the problem is solved. >
So this puts another spot-light on a general but yet not fully understood problem. If darktable re-imports an image that it has seen before it gets into trouble. This seems to be solved by my recent commit which forces the database to always give a fresh ID to all new images, also to re-imported ones (autoincrement on key field). For all new installations (with newly generated library.db) the problem is solved. Unfortunately all existing library.db files still have the issue. sqlite does not allow to change the autoincrement property on existing tables. I am thinking about a migration tool (small python script). However, any error in that will screw your library.db and leave you without your presets, styles and settings. So I better double check that it works properly. Ulrich ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
