Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 2EA272E002C for ; Tue, 22 Apr 2008 12:16:55 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 84210-05 for ; Tue, 22 Apr 2008 12:16:46 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.186]) by developer.postgresql.org (Postfix) with ESMTP id 044992E0065 for ; Tue, 22 Apr 2008 12:16:45 -0300 (ADT) Received: by rn-out-0910.google.com with SMTP id i24so850428rng.0 for ; Tue, 22 Apr 2008 08:16:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=mY7jO1fVQ0aVHzIXC84egTTmC3zILeKrLT/Phq5NhAk=; b=aMA0uWl4ZMyD2MwtNqdEQ+tUiefNrGiWkLUP17qaQxOIDV6QvJmtXoka4yR+/uKOCoRp3o20eZnBSpI6aqwjN5YwvK34BN69qFDAZz4YgW11f+Kw+DyW4SGvywRylzeDoL2TrT6hmBWMNARdcdeuFcQOqIumRS5A6YyFaE0Ul9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eNUPCLFd/28HVmSrHnnv6ui+CitQ/sFfn6O2QGS7WDkkq4szgeynyV7/LnXzv6oQfQPXNIUWeAUrcjW7nqt/s47WOrwoONRZoWhHvsj3n9Q0maNae3LGCM6TWDrPz5iscu9cKgnABzHUeimcOnqiHm3bAlXAFNuda//uy83AwKg= Received: by 10.115.89.1 with SMTP id r1mr376400wal.195.1208877404490; Tue, 22 Apr 2008 08:16:44 -0700 (PDT) Received: by 10.114.137.7 with HTTP; Tue, 22 Apr 2008 08:16:44 -0700 (PDT) Message-ID: Date: Tue, 22 Apr 2008 09:16:44 -0600 From: "Scott Marlowe" To: "Nacef LABIDI" Subject: Re: After updating dataset the record goes to the end of thedataset Cc: "Bart Degryse" , "Craig Ringer" , pgsql-sql@postgresql.org, "Roland Voegtli" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <480DDE26.50405@postnewspapers.com.au> <480DFC7F.A3DD.0030.0@indicator.be> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/141 X-Sequence-Number: 30680 On Tue, Apr 22, 2008 at 7:00 AM, Nacef LABIDI wrote: > Thank you all for your useful comments. > > I have tried to order my records as you said and got it work as I wanted. Cool beans! I was just watching this conversation, but wanted to point out that using the methods mentioned in this thread (i.e. ones that use order by) is good practice. It's quite possible that at some point in the future the storage engine of MS-SQL could change and break your application on that platform. By using the order by method, you ensure you're using a method that works today and in the future on all major platforms.