Re: [Fwd: Re: no ORDER BY in subselects?]

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: [Fwd: Re: no ORDER BY in subselects?]
Date: 2000-09-22 15:01:06
Message-ID: web-1091623@davinci.ethosmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2000-09-22 16:51:32 Re: sql query not using indexes
Previous Message root 2000-09-22 13:58:56 how to store a query, that results in a table