From: Markus Bertheau <twanger@bluetwanger.de>
To: Jean-Luc Lachance <jllachan@sympatico.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: SELECT MAX(c) FROM (SELECT ... FOR UPDATE) AS foo
Date: Tue, 17 Aug 2004 16:51:21 +0200
Message-ID: <1092754281.2627.28.camel@dicaprio.akademie1.de> (raw)
In-Reply-To: <41221580.7070907@sympatico.ca>
References: <1092740863.2627.17.camel@dicaprio.akademie1.de>
<41221580.7070907@sympatico.ca>
В Втр, 17.08.2004, в 16:26, Jean-Luc Lachance пишет:
> This query does not make sense to me.
> Why would you create an updatable subquery just to get the highest value?
To make sure that the highest value will be the highest value (or then
second-highest) after I commit the transaction. See my other answer.
--
Markus Bertheau <twanger@bluetwanger.de>
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: twanger@bluetwanger.de, jllachan@sympatico.ca
Subject: Re: SELECT MAX(c) FROM (SELECT ... FOR UPDATE) AS foo
In-Reply-To: <1092754281.2627.28.camel@dicaprio.akademie1.de>
* 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