From: Josh Berkus <josh@agliodbs.com>
To: pgsql-sql@postgresql.org
Subject: Re: [Fwd: Re: no ORDER BY in subselects?]
Date: Fri, 22 Sep 2000 08:01:06 -0700
Message-ID: <web-1091623@davinci.ethosmedia.com> (raw)
In-Reply-To: <3.0.5.32.20000921112954.00c9be00@mail.rhyme.com.au>
Phillip,
> The main reason I use them is to find the 'next' or
> 'previous' record in a
> list (eg. next date, next ID). eg.
> The fact that Dec RDB, Oracle and SQL/Server all allow it
> probably means
> that there is a reasonable user base out there who think
> it's a good idea.
Makes sense. Fortunately, in PGSQL there's another function
to grab the next ID. As for dates ... hmmm... there we come
up against the "no subselect in FROM" bug, don't we? I get
the problem.
(Personally, I've always SELECTed into a variable in MSSQL
rather than using the syntac you're suggesting. I've found
that the order that the MSSQL chooses to execute query
segments in can cause some unpredicatble results ... )
-Josh Berkus
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: [Fwd: Re: no ORDER BY in subselects?]
In-Reply-To: <web-1091623@davinci.ethosmedia.com>
References: <3.0.5.32.20000921112954.00c9be00@mail.rhyme.com.au> <web-1091623@davinci.ethosmedia.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