Repeatable reads

It appears that postgres 7.0 does not support repeatable read for
transaction isolation. Is this planned? If so, when?

-Michael
_________________________________________________________________
http://fastmail.ca/ - Fast Free Web Email for Canadians
>From pgsql-sql-owner(at)hub(dot)org Tue Sep 19 14:09:07 2000
Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
by hub.org (8.10.1/8.10.1) with ESMTP id e8JI95s40367
for <pgsql-sql(at)postgresql(dot)org>; Tue, 19 Sep 2000 14:09:05 -0400 (EDT)
Received: from [206.169.43.135] (HELO agliodbs.com)
by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.3)
with ESMTP id 1090499 for pgsql-sql(at)postgresql(dot)org; Tue, 19 Sep 2000 11:09:04 -0700
Message-ID: <39C7AB0E(dot)FA901CF8(at)agliodbs(dot)com>
Date: Tue, 19 Sep 2000 11:06:06 -0700
From: Josh Berkus <josh(at)agliodbs(dot)com>
Reply-To: josh(at)agliodbs(dot)com
Organization: Aglio Database Solutions
X-Mailer: Mozilla 4.73 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sqllist <pgsql-sql(at)postgresql(dot)org>
Subject: Re: sum of agreggates in one SELECT?
References: <20000919125859(dot)A2802(at)styx> <7125(dot)969384468(at)sss(dot)pgh(dot)pa(dot)us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200009/137

Tom,

> You can't have aggregates of aggregates in a single SELECT structure;
> that's just not in the SQL execution model. The way around this is
> to write multiple levels of SELECT, using either selection from a
> grouped/aggregated view or subselect-in-FROM. Unfortunately Postgres
> doesn't have either of those features --- yet. They might be in 7.1
> if I spend less time answering email and more time coding...

Well, stop answering your e-mail, then, dammit!
(impatiently waiting for 7.1)

Seriously, you could actually slack (as in wait 8-12 hours) on answering
the questions. There's been several basic SQL questions I could have
fielded and you answered them first.

Unfortunately, Louis-David, I don't see any way around subselects in the
FROM clause as Tom mentions, which are not currently supported. I'd
suggest using a Function to create a temporary table or view and
summarizing from that.

-Josh Berkus

--
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 436-9166
for law firms, small businesses fax 436-0137
and non-profit organizations. pager 338-4078
San Francisco