| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jonathan <jharahush(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: haversine formula with postgreSQL |
| Date: | 2009-09-17 21:47:49 |
| Message-ID: | 4642.1253224069@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jonathan <jharahush(at)gmail(dot)com> writes:
> Here is my PHP with SQL:
> $query = sprintf("SELECT 'ID', 'FACILITY', 'ADDRESS', latitude,
> longitude, ( 3959 * acos( cos( radians('%s') ) * cos( radians
> ( latitude ) ) * cos( radians( longitude ) - radians('%s') ) + sin
> ( radians('%s') ) * sin( radians( latitude ) ) ) ) AS distance FROM
> aaafacilities HAVING distance < '%s' ORDER BY dist LIMIT 0 OFFSET 20",
Sigh, you've been misled by MySQL's nonstandard behavior. You cannot
refer to output columns of a query in its HAVING clause; it's disallowed
per spec and not logically sensible either. The simplest way to deal
with it is just to repeat the expression in HAVING. If you really
really don't want to write it twice, you can use a subquery.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Gainty | 2009-09-17 21:56:38 | Re: 'Weird' errors |
| Previous Message | Tom Lane | 2009-09-17 21:39:45 | Re: Row estimates on empty table |