Hi Nils, thanks for your reply.
Database transactions help in terms of integrity, but they can do nothing about
the order of data updates. If 2 threads work independently and execute the same
update query on the db, I can't predict with certainty which one will occur
first.
Fabio
Il giorno
Fabio Sangiovanni wrote:
Database transactions help in terms of integrity, but they can do nothing
about the order of data updates. If 2 threads work independently and execute
the same update query on the db, I can't predict with certainty which one
will occur first.
AFAIK no updates are
Hi, thanks for your reply.
Il giorno 30/dic/2011, alle ore 09:43, bert hubert ha scritto:
On Thu, Dec 29, 2011 at 08:55:57AM +, Fabio Sangiovanni wrote:
am I right thinking this would solve my problem?
For now, and for this version of the PowerDNS Recursor, if you set threads
to 1, you will
Ok I'm kind of a newbie here :)
My understanding of the problem is:
if I have 2 threads, running at the same time, both of them executing the same
SQL transaction (made up of more select or update queries), how can I predict
which one is executed first? It's just like you said: I'd need the
Ok fixed this one temporary by my self by adding
else if(db-isMaster(p-qdomain, p-getRemote())) {
LLogger::ErrorReceived NOTIFY for p-qdomain from
p-getRemote()endl;
//return RCode::Refused;
}
Under
else if(!db-isMaster(p-qdomain, p-getRemote())) {
On Fri, Dec 30, 2011 at 10:00:50AM +, Fabio Sangiovanni wrote:
Ok I'm kind of a newbie here :)
My understanding of the problem is:
if I have 2 threads, running at the same time, both of them executing the
same SQL transaction (made up of more select or update queries), how can I
predict
