From: | Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> |
---|---|
To: | Josué Maldonado <josue(at)lamundial(dot)hn> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Record order change after update |
Date: | 2004-06-10 13:49:34 |
Message-ID: | 1086875373.913.6.camel@taz.oficina |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?
>
> Thanks in advance.
>
> Josué Maldonado
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | James Pharaoh | 2004-06-10 14:05:56 | Re: Transactions and insertion ordering |
Previous Message | Bruno Wolff III | 2004-06-10 13:47:34 | Re: Transactions and insertion ordering |