hey,
On Tue, Jul 30, 2013 at 7:14 AM, Wolfgang Beutner
<[email protected]>wrote:
> I opened the database with the firefox plugin SQLite manager.
i would recommend sqlite3 the command line tool for this.
> There is a
> table called 'history' which contains some of the modifications but not
> all.
yes it does. for newly imported images it will be populated from
auto-applying presets in table `presets'.
> Maybe I'm wrong with the table, but history sounds right. Maybe
> when the program crashes they are not written to the table. But when I
> take a look at them the changes are still there, perhaps loaded from the
> sidecar file. I just want to understand because I'm a bit uncertain with
> DT. Has some fine features, but lacks stability. Using the latest
> version from git, since my camera was not detected by older ones.
>
> i only use git master for production work and it never crashes (i guess
i'm not using newer features too much).
> I got all the information from the last crash, is that of any interest?
>
i think this is the third time you mail about a crash without steps to
reproduce or a stack trace. will you enlighten us about that at some point
or are you just making it up :) ?
cheers,
jo
I would like to help improve DT, but for the moment I think I cannot do
> much besides trying to find reproducible errors.
>
> Wolfgang
>
> Am 29.07.2013 21:01, schrieb Jose Carlos Garcia Sogo:
> > On Mon, Jul 29, 2013 at 8:58 PM, Wolfgang Beutner
> > <[email protected]> wrote:
> >> I'm trying to understand the way DT stores its information in the
> >> database. I thought every change would be represented there. Now I found
> >> that some changes are not in the history table. Even those that were
> >> applied when loading the images (sharpen and basecurve). I would like to
> >> have some more infos on that. Is there anything available about the
> >> tables and there contents?
> > They will be stored when you leave darkroom mode, or you switch to
> > another image. In the meantime, they are kept in a GList.
> >
> >> Regards, Wolfgang
> >>
> >>
> ------------------------------------------------------------------------------
> >> Get your SQL database under version control now!
> >> Version control is standard for application code, but databases havent
> >> caught up. So what steps can you take to put your SQL databases under
> >> version control? Why should you start doing it? Read more to find out.
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> >> _______________________________________________
> >> darktable-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/darktable-devel
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> darktable-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
