If I have two threads modifying the same bit field:
thread1= update table set bf=bf | '01000'
thread2= update table set bf=bf | '1'
Will this operation always be safe (e.g. result in bf='11000')? Or
Won't this always result in bf='11xxx', depending on the
original values of bf?
TJ O'Donnell wrote:
If I have two threads modifying the same bit field:
thread1= update table set bf=bf | '01000'
thread2= update table set bf=bf | '1'
Will this operation always be safe (e.g. result in bf='11000')? Or
Won't this always result in bf='11xxx', depending on
Dear List;
If I have two threads modifying the same bit field:
thread1= update table set bf=bf | '01000'
thread2= update table set bf=bf | '1'
Will this operation always be safe (e.g. result in bf='11000')? Or must
I wrap things in
explicit transactions?
My application is to give
Bryce Nesbitt wrote:
If I have two threads modifying the same bit field:
thread1= update table set bf=bf | '01000'
thread2= update table set bf=bf | '1'
Will this operation always be safe (e.g. result in bf='11000')? Or
must I wrap things in
explicit transactions?
Each of these
Am Sonntag, 26. März 2006 23:47 schrieb Bryce Nesbitt:
Dear List;
If I have two threads modifying the same bit field:
thread1= update table set bf=bf | '01000'
thread2= update table set bf=bf | '1'
Will this operation always be safe (e.g. result in bf='11000')?
yes, Thats what
