Received: from localhost (unknown [200.46.204.183])
	by developer.postgresql.org (Postfix) with ESMTP id D05092E0046
	for <pgsql-sql-postgresql.org@developer.postgresql.org>;
	Tue, 22 Apr 2008 07:10:46 -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 65090-07
	for <pgsql-sql-postgresql.org@developer.postgresql.org>;
	Tue, 22 Apr 2008 07:10:43 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237])
	by developer.postgresql.org (Postfix) with ESMTP id 12E4A2E004C
	for <pgsql-sql@postgresql.org>; Tue, 22 Apr 2008 07:10:42 -0300 (ADT)
Received: by wx-out-0506.google.com with SMTP id r21so1730569wxc.28
	for <pgsql-sql@postgresql.org>; Tue, 22 Apr 2008 03:10:42 -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:in-reply-to:mime-version:content-type:references;
	bh=og7WSPBd5aM6/D/EkJWNdCZ/R2FBhudVYWFRA3Rhvaw=;
	b=nO07TLhW394AS4J0XG5bGk0wC4QEi9vtwEZAwDa8BO1VLbT2/4Ahit9EjhyKf1p7ZnQWfMkHs4EBAyvJ43q75QW9y5ymVPgNhlikJVXQqlFdFlz+1kajfsv2Pb4O8ThBkcpKktlXuOg+yAzpAXlKOFQsLGUM7wMntqhPHPtBbWo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=gUG34rHcVzEn/D/Zd0iOtLkaIWLvGcmKrAZJvePa/XEr72P9//o1YfmXYkpyTUJKGE2mzXY3MpE0y2HgMhUmfglZjmPQux+NPzJw8jTRnWI1KonbqUmj8FP3Z8+2WwuqaJWuVghTNlLMwD6CkatI5Y5CtwWhTWf7svHLv6FUhIA=
Received: by 10.70.19.7 with SMTP id 7mr6214wxs.33.1208859041973;
	Tue, 22 Apr 2008 03:10:41 -0700 (PDT)
Received: by 10.70.25.5 with HTTP; Tue, 22 Apr 2008 03:10:41 -0700 (PDT)
Message-ID: <f16f7ea00804220310m26753072mec98ef0bc6bb2c9e@mail.gmail.com>
Date: Tue, 22 Apr 2008 12:10:41 +0200
From: "Nacef LABIDI" <nacef.l@gmail.com>
To: "Roland Voegtli" <voegtli@scnat.ch>, pgsql-sql@postgresql.org
Subject: Re: After updating dataset the record goes to the end of the dataset
In-Reply-To: <3B256469-4A00-44C3-8EB8-F49FA9F7259A@scnat.ch>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2588_5387726.1208859041960"
References: <f16f7ea00804220254i671e446au7c50dca45dea10d7@mail.gmail.com>
	<3B256469-4A00-44C3-8EB8-F49FA9F7259A@scnat.ch>
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/129
X-Sequence-Number: 30668

------=_Part_2588_5387726.1208859041960
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes I don't issue any sort statement, and I indeed want the data to be show
as it is stored in the database. But after updating a row (I don't update
the ID, just some fields), it keeps its same place on the DB but jumps to
the end of the dataset and by the way to the end of the DBGrid.

Nacef

On Tue, Apr 22, 2008 at 12:06 PM, Roland Voegtli <voegtli@scnat.ch> wrote:

> Has anyone an idea about what could be the cause of such a behavior.
> >
>
> You don't issue any sort statement with the query, obviously. So you get
> the records the way they are stored in the database.
>
> cheers
> (R)
>
>

------=_Part_2588_5387726.1208859041960
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes I don&#39;t issue any sort statement, and I indeed want the data to be show as it is stored in the database. But after updating a row (I don&#39;t update the ID, just some fields), it keeps its same place on the DB but jumps to the end of the dataset and by the way to the end of the DBGrid.<br>
<br>Nacef<br><br><div class="gmail_quote">On Tue, Apr 22, 2008 at 12:06 PM, Roland Voegtli &lt;voegtli@scnat.ch&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Has anyone an idea about what could be the cause of such a behavior.<br>
</blockquote>
<br></div>
You don&#39;t issue any sort statement with the query, obviously. So you get the records the way they are stored in the database.<br>
<br>
cheers<br>
&reg;<br>
<br>
</blockquote></div><br>

------=_Part_2588_5387726.1208859041960--