X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5086052965 for ; Thu, 31 Mar 2005 01:04:15 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98378-07 for ; Thu, 31 Mar 2005 00:04:05 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9C2775295D for ; Thu, 31 Mar 2005 01:04:04 +0100 (BST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 736BA30952; Thu, 31 Mar 2005 02:04:03 +0200 (MET DST) From: Chris Browne X-Newsgroups: pgsql.sql Subject: Re: New record position Date: Wed, 30 Mar 2005 18:04:27 -0500 Organization: cbbrowne Computing Inc Lines: 21 Message-ID: <60br90spl0.fsf@dba2.int.libertyrms.com> References: <20050330105017.miuieky7u64gscgc@www.presserv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:2SInDXOmI4P11pk/ZqtYmtIP+6E= To: pgsql-sql@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.178 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/402 X-Sequence-Number: 20881 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