Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9A740475EB2 for ; Fri, 13 Sep 2002 11:34:29 -0400 (EDT) Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by postgresql.org (Postfix) with SMTP id DFAC4475D0D for ; Fri, 13 Sep 2002 11:34:28 -0400 (EDT) Received: from psc.progress.com (HELO Yahoo.com) (janwieck@192.233.92.200 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 13 Sep 2002 15:22:22 -0000 Message-ID: <3D8201EF.CB5F3BD6@Yahoo.com> Date: Fri, 13 Sep 2002 11:19:11 -0400 From: Jan Wieck Organization: Home X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru MIME-Version: 1.0 To: Tim Perdue Cc: Larry Rosenman , pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] Latitude / Longitude References: <20020912124426.A27570@mail.perdue.net> <1031852961.380.20.camel@lerlaptop.iadfw.net> <20020912144957.F27651@mail.perdue.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/531 X-Sequence-Number: 30112 Tim Perdue wrote: > > On Thu, Sep 12, 2002 at 12:49:21PM -0500, Larry Rosenman wrote: > > Look at contrib/earthdistance, I **think** it does what you need. > > Thanks, yeah this starts to get me into the realm of what I need. It still > has to run every possible permutation to figure out which one is closest for > each postalcode. What I'll do is run that once and build a 3rd table which can > be used to join the other two together using a view. That third table should be maintained by triggers and constraints, no? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #