In article <[EMAIL PROTECTED]>,
Alex Adriaanse <[EMAIL PROTECTED]> writes:
> Thanks for the input everyone. I think Harald's approach will work
> well...
I'm not so sure anymore :-(
Consider something like that:
UPDATE tbl SET col1 = 1 WHERE col2 = 1;
UPDATE tbl SET col1 = 2 WHERE col2 = 1;
with not much time inbetween. By using NULL temporarily, you destroy
the ordering. The client won't miss an UPDATE, but it might execute
the second one before the first. Neither my nor your idea appear to
take care of that.
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
