On Wed, Oct 30, 2013 at 11:04 AM, Pascal Obry <[email protected]> wrote:
>
> Johannes,
>
> > how did you import the images in the first place? recursively in subdirs?
> >
> > some exif data is cached in the db, so reimport without removing them
> > from db first wouldn't do anything.
> >
> > i don't like the sounds of it because it seems we have inconsistent data
> > in the db? if you still have such a broken film roll, is there anything
> > obviously wrong with the image record in our sqlite3 database?
>
> I think I had one instance of this problem recently but was not able to
> make sense of it and after reimporting all was ok.
>
> The "images" table for the newly imported pictures was fill with 0. That
> is 0 for integer/real rows and null string for the varchar. Really strange!
>
there is a report on irc about a case where data was initially present and
got zeroed out at some point. since we don't really write that stuff into
db any more it might have happened during back-syncing of the image cache.
so maybe there is a case where someone memset(0)'s the dt_image_t and then
syncs it back to the cache? that'll be very hard to debug, could be
everywhere. maybe we should just put an assertion into
dt_image_cache_write_release() and wait for crash reports..?
-jo
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
