From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Doug McNaught <doug(at)wireboard(dot)com> |
Cc: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: calculating spherical distance in sql |
Date: | 2002-02-18 05:38:26 |
Message-ID: | 6052.1014010706@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Doug McNaught <doug(at)wireboard(dot)com> writes:
> Define "didn't work".
"Didn't work" no doubt means "a column name defined in the SELECT's
output list is not available in the SELECT's where clause".
The way you could actually suppress multiple calculations of an
expression is to use a sub-SELECT:
SELECT *
FROM
(SELECT z.zip_code,z.poname,z.state,
(3958.75 *
acos(
sin(s.latitude/57.2958) *
sin(z.latitude/57.2958) +
cos(s.latitude/57.2958) *
cos(z.latitude/57.2958) *
cos(z.longitude/57.2958 - s.longitude/57.2958)
)
) AS dist
FROM zipcodes AS z, zipcodes AS s
WHERE s.zip_code='55401'
) AS ss
WHERE dist < 20
ORDER BY dist LIMIT 10;
I'm not convinced that it buys much in this example, but with a
*seriously* expensive expression to calculate, it might be worth
contorting your query like this...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Emberson | 2002-02-18 05:52:30 | text vs varchar(n) |
Previous Message | Doug McNaught | 2002-02-18 05:19:59 | Re: calculating spherical distance in sql |