Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id E66B62E0061 for ; Tue, 22 Apr 2008 10:00:55 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 28661-01-2 for ; Tue, 22 Apr 2008 10:00:38 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.190]) by developer.postgresql.org (Postfix) with ESMTP id CD4D32E0091 for ; Tue, 22 Apr 2008 10:00:24 -0300 (ADT) Received: by gv-out-0910.google.com with SMTP id y18so234886gvf.7 for ; Tue, 22 Apr 2008 06:00:23 -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:references; bh=eh94xR1y8ZAECMh0YTbKc51a/8PulmT+JIt8HD9jQLY=; b=NahUlR+bDlNqNfIZN894i+DQEk4oO8EQTeqRq783Q5bgyO1pc0ycKfcukMJOtft4l9HGx2G1KjgajLPYpyrXzCCLjF0ohV4Kv5y7cbeC/Y5jSV93FKEU87qxhih4Jj0UXbnXfkOxdkPmTCYZlNmgRW1l/4LOJpa2ojbb0Y3unbU= 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:references; b=lDXy/G0Qpn8HkJ1QyjNIkdLFi0Vy/0/FcskVoaxAIXmIB+bV0WBWRJB9mJHQJqbm/dh8p/0riJBwPG22R08o5z+25NZCNu/tFHr6aZZGBJ5qk9cAdGwLFSjpenH3dQ2tg9pPOfQ2rDzfva453v2GEhCq/oMnFbev9Of9EeUEhY4= Received: by 10.150.205.13 with SMTP id c13mr162523ybg.132.1208869222004; Tue, 22 Apr 2008 06:00:22 -0700 (PDT) Received: by 10.70.25.5 with HTTP; Tue, 22 Apr 2008 06:00:21 -0700 (PDT) Message-ID: Date: Tue, 22 Apr 2008 15:00:21 +0200 From: "Nacef LABIDI" To: "Bart Degryse" Subject: Re: After updating dataset the record goes to the end of thedataset Cc: "Craig Ringer" , pgsql-sql@postgresql.org, "Roland Voegtli" In-Reply-To: <480DFC7F.A3DD.0030.0@indicator.be> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3111_22105555.1208869221994" References: <480DDE26.50405@postnewspapers.com.au> <480DFC7F.A3DD.0030.0@indicator.be> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200804/139 X-Sequence-Number: 30678 ------=_Part_3111_22105555.1208869221994 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thank you all for your useful comments. I have tried to order my records as you said and got it work as I wanted. Thank you again On Tue, Apr 22, 2008 at 2:56 PM, Bart Degryse wrote: > Probably what you mean is that you want the order in which the records > were > originally inserted into the database. In that case add a serial to your > table and > fetch the records like > SELECT * FROM tbl WHERE 1=1 ORDER BY [myserialfield] > It's not foolproof but will in many cases come close to what you seem to > be trying > to achieve by not using 'order by'. > > Nacef LABIDI wrote: > > Yes I don't issue any sort statement, and I indeed want the data to be > show > > as it is stored in the database. > ------=_Part_3111_22105555.1208869221994 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thank you all for your useful comments.

I have tried to order my records as you said and got it work as I wanted.

Thank you again

On Tue, Apr 22, 2008 at 2:56 PM, Bart Degryse <Bart.Degryse@indicator.be> wrote:
Probably what you mean is that you want the order in which the records were
originally inserted into the database. In that case add a serial to your table and
fetch the records like
SELECT * FROM tbl WHERE 1=1 ORDER BY [myserialfield]
It's not foolproof but will in many cases come close to what you seem to be trying
to achieve by not using 'order by'.


Nacef LABIDI wrote:
> Yes I don't issue any sort statement, and I indeed want the data to be show
> as it is stored in the database.

------=_Part_3111_22105555.1208869221994--