I’m starting to get some optimistic column locking failures during background
db processing soI’m trying to grasp conditions under which I don’t need to lock
a column (i.e. put the little lock symbol in EOModeler)
If I have a column in a table that I know is not updated (i.e. changed) by any
c
Hi Jeff,
Yes, if a column is not marked as locking, then it won’t appear in the WHERE
clause.
The danger is that you might save changes that are inconsistent with what the
database has stored in the columns that you are not locking on. As a contrived
example, consider the update below changin
Jeff, if you remove the lock, you have a risk to get a write-write conflict,
aka a write replaced by another. It’s maybe not a big deal. I don’t know.
Another solution, if you are sure your background db process is the only one to
modify an attribute, is to use raw sql to update the column you w
Hi Markus,
my build files have a section that looks exactly like the one you posted, so
that’s not a solution.
Note: I’m not making URLs for WebServerResources, the Resources in question are
from “Resources”.
- hugi
> On 16. mar. 2016, at 10:44, Dr. Markus Stoll, junidas GmbH
> wrote:
>
