ssing data with integrity guaranteed provided you are
using it within a single read consistent query and not storing its value for
reuse.
Rgds,
Rob.
From: johannes hanika [mailto:hana...@gmail.com]
Sent: 20 October 2013 08:36
To: Pascal Obry
Cc: darktable-devel
Subject: Re: [darktable-devel] pr
Le 20/10/2013 09:35, johannes hanika a écrit :
> oh. my understanding of the sqlite docs is that rowid is just an
> internal thing that we shouldn't rely on because they reserve the right
> to change what it does between versions etc?
Right.
> i'm totally for an additional id in this case.. there
oh. my understanding of the sqlite docs is that rowid is just an internal
thing that we shouldn't rely on because they reserve the right to change
what it does between versions etc?
i'm totally for an additional id in this case.. there is some sql update
path somewhere around control_init() (contr
The problem is the following.
The styles are numbered after its rowid (table styles)
The styles items have a styleid referencing the style above.
When a style is removed the rowid are non continuous, that is:
sqlite> select rowid,* from styles;
1|red|
3|blue|
4|violet|
The rowid is style refe
