From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: question about visibilty while updating multiple rows .
Date: Thu, 10 Apr 2003 10:11:19 +0530
Message-ID: <200304101011.20087.mallah@trade-india.com> (raw)
In-Reply-To: <7045.1049901168@sss.pgh.pa.us>
References: <200304091247.59378.mallah@trade-india.com>
<7045.1049901168@sss.pgh.pa.us>
On Wednesday 09 Apr 2003 8:42 pm, Tom Lane wrote:
> > If an update statement is affecting multiple rows of a table X ,
> > Does a subselect (selecting from X only) inside EXISTS part of outer
> > query able to see the changes when rows are being updated one by one by
> > outer query?
>
> No, because it's part of the same query.
>
> I believe though that a user-defined function called from the update
> query would see the changes made so far. So possibly you can fix your
> problem by pushing the EXISTS down into a SQL or plpgsql function.
Thanks for the explanation and suggestion Tom,
I did it however by using intermediate tables and distinct on().
Regds
Mallah.
>
> regards, tom lane
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mallah@trade-india.com, tgl@sss.pgh.pa.us
Subject: Re: question about visibilty while updating multiple rows .
In-Reply-To: <200304101011.20087.mallah@trade-india.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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