From: Chris Browne <cbbrowne@acm.org>
To: pgsql-sql@postgresql.org
Subject: Re: New record position
Date: Wed, 30 Mar 2005 18:04:27 -0500
Message-ID: <60br90spl0.fsf@dba2.int.libertyrms.com> (raw)
References: <20050330105017.miuieky7u64gscgc@www.presserv.org>
lucas@presserv.org writes:
> Why it? I can't undestand why the new record location was change. Shouldn't it
> apper at the LAST record???
> What need I do??
SQL only imposes an order on the return set if you add an "ORDER BY"
clause.
You can't expect any particular order to either recur or NOT recur
unless you have specifically requested a particular ordering.
There's no bug; just use ORDER BY if you need to, and, if you don't,
make sure you don't expect any particular ordering...
--
(format nil "~S@~S" "cbbrowne" "cbbrowne.com")
http://www3.sympatico.ca/cbbrowne/spiritual.html
"The present need for security products far exceeds the number of
individuals capable of designing secure systems. Consequently,
industry has resorted to employing folks and purchasing "solutions"
from vendors that shouldn't be let near a project involving securing a
system." -- Lucky Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: New record position
In-Reply-To: <60br90spl0.fsf@dba2.int.libertyrms.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox