Re: Another unexpected behaviour - Mailing list pgsql-general

From Rob Richardson
Subject Re: Another unexpected behaviour
Date
Msg-id 04A6DB42D2BA534FAC77B90562A6A03D0193B117@server.rad-con.local
Whole thread Raw
In response to Re: Another unexpected behaviour  (Samuel Hwang <samuel@replicon.com>)
Responses Re: Another unexpected behaviour
List pgsql-general
It seems to me that it is inherently wrong to perform any operation on a
database that depends on the order in which records are retrieved,
without specifying that order in an ORDER BY clause.  The "update t1 set
f1 = f1 + 1" assumes that the operation will be performed in an order
that guarantees that the highest unchanged record will be the next
record processed.  I don't believe that any database system should be
required to support an action like this.

RobR

pgsql-general by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Another unexpected behaviour
Next
From: Rick Genter
Date:
Subject: Re: Another unexpected behaviour