From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> |
Cc: | Josué Maldonado <josue(at)lamundial(dot)hn>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Record order change after update |
Date: | 2004-06-10 14:16:12 |
Message-ID: | 878yev4hxv.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-10 14:22:14 | Re: How to tell when postmaster is ready |
Previous Message | James Pharaoh | 2004-06-10 14:05:56 | Re: Transactions and insertion ordering |