Re: Record order change after update - Mailing list pgsql-general

From Doug McNaught
Subject Re: Record order change after update
Date
Msg-id 878yev4hxv.fsf@asmodeus.mcnaught.org
Whole thread Raw
In response to Re: Record order change after update  (Franco Bruno Borghesi <franco@akyasociados.com.ar>)
List pgsql-general
Franco Bruno Borghesi <franco@akyasociados.com.ar> writes:

>    >From the relational point of view, tuples in a relation are sets, and
>    sets have no ordering.
>    That's why you should never trust how tuples are ordered (on any
>    relational database, not just postgreSQL), and if you care about
>    ordering you should always use the ORDER BY clause.
>    On Tue, 2004-03-02 at 19:12, Josué Maldonado wrote:
>
> Hello list,
>
> After update a column on a table, that row goes to the top when I do a
> select from that table without any order, is that the expected behavior
> in postgresql? is there a way to prevent it?

The paragraph you quoted above answers your question.  Use ORDER BY if
you want a definite order out of a SELECT query.

-Doug

pgsql-general by date:

Previous
From: James Pharaoh
Date:
Subject: Re: Transactions and insertion ordering
Next
From: Tom Lane
Date:
Subject: Re: How to tell when postmaster is ready