| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | sqllist <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Outer Joins |
| Date: | 2000-11-02 16:37:32 |
| Message-ID: | 3A01984C.7FFE3B90@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Marc,
> >This would work, but it would be *much* slower than a UNION query. "Not
> >In" queries are perhaps the slowest you can run; see the earlier thread
> >"Query Problem" for a discussion. UNION queries are, in fact, very fast
> >... just awkward to code and manipulate.
>
> Why should this be slower since the UNION Query still has an identical not in clause?
> This is far easier (for me) to read.
Good point. Frankly, if you have a relevant large population of data
(>10,000 rows) to test, I'd love to see comparative execution tests
between the two query structures.
Fortunately, this will all soon become moot; Tom says that outer joins
have been stable in the 7.1 build for a while. Speaking of which,
when's the 7.1 "release"? Huh, huh?
-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2000-11-02 16:55:36 | Re: Outer Joins |
| Previous Message | Tom Lane | 2000-11-02 08:09:10 | Re: [SQL] Re: Problem with coalesce.. |