Re: PostgreSQL versus MySQL for GPS Data

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Juan Pereira <juankarlos(dot)openggd(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL versus MySQL for GPS Data
Date: 2009-03-17 15:11:30
Message-ID: 49BFBDA2.50401@postnewspapers.com.au
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general

Stephen Frost wrote:

> As mentioned, you might want to eliminate duplicate entries; no sense
> storing information that can be trivially derived.

It's pretty easy to do that with a trigger - and you can add a degree of
noise correction too, so that "wobble" in GPS position doesn't get
recorded - you only log changes of more than a certain distance.

--
Craig Ringer

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Stephen Frost 2009-03-17 15:54:51 Re: PostgreSQL versus MySQL for GPS Data
Previous Message Scott Marlowe 2009-03-17 15:06:27 Re: PostgreSQL versus MySQL for GPS Data

Browse pgsql-general by date

  From Date Subject
Next Message Neanderthelle Jones 2009-03-17 15:17:50 Re: Escaping special characters
Previous Message Raymond O'Donnell 2009-03-17 15:10:44 Re: COPY command question