pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedsequence chages after firing update
3+ messages / 3 participants
[nested] [flat]
* sequence chages after firing update
@ 2002-06-26 11:47 Subhashini Karthikeyan <subhaksekar@yahoo.com>
0 siblings, 2 replies; 3+ messages in thread
From: Subhashini Karthikeyan @ 2002-06-26 11:47 UTC (permalink / raw)
To: pgsql-sql
hi all
In postgresql 7.1.3
i am updateing a row. it is a 4th record.
after updation if i am firing a select query it is
coming as a last record ..what shall i do to avoid
that..
any help appriciated
thankz in advance
regards
subha
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: sequence chages after firing update
@ 2002-06-26 14:46 Stephan Szabo <sszabo@megazone23.bigpanda.com>
parent: Subhashini Karthikeyan <subhaksekar@yahoo.com>
1 sibling, 0 replies; 3+ messages in thread
From: Stephan Szabo @ 2002-06-26 14:46 UTC (permalink / raw)
To: Subhashini Karthikeyan <subhaksekar@yahoo.com>; +Cc: pgsql-sql
On Wed, 26 Jun 2002, Subhashini Karthikeyan wrote:
> In postgresql 7.1.3
>
> i am updateing a row. it is a 4th record.
> after updation if i am firing a select query it is
> coming as a last record ..what shall i do to avoid
> that..
> any help appriciated
If I understand the complaint, use an order by to
force an order on the select. You can't guarantee the
order rows are returned to you unless you do (different
plans might give you rows in different orders anyway)
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: sequence chages after firing update
@ 2002-06-26 15:18 Rajesh Kumar Mallah. <mallah@trade-india.com>
parent: Subhashini Karthikeyan <subhaksekar@yahoo.com>
1 sibling, 0 replies; 3+ messages in thread
From: Rajesh Kumar Mallah. @ 2002-06-26 15:18 UTC (permalink / raw)
To: Subhashini Karthikeyan <subhaksekar@yahoo.com>; pgsql-sql
dear subha,
Use explicit ORDER BY if u want to order the records
by some column.
otherwise the order of output from a select stmt is undefined.
bu generally it is found the the last updated record comes last.
On Wednesday 26 June 2002 17:17, Subhashini Karthikeyan wrote:
> hi all
>
>
> In postgresql 7.1.3
>
> i am updateing a row. it is a 4th record.
> after updation if i am firing a select query it is
> coming as a last record ..what shall i do to avoid
> that..
> any help appriciated
>
> thankz in advance
>
> regards
> subha
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)
Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2002-06-26 15:18 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-06-26 11:47 sequence chages after firing update Subhashini Karthikeyan <subhaksekar@yahoo.com>
2002-06-26 14:46 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
2002-06-26 15:18 ` Rajesh Kumar Mallah. <mallah@trade-india.com>
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