From: | Juan Pereira <juankarlos(dot)openggd(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | PostgreSQL versus MySQL for GPS Data |
Date: | 2009-03-17 11:25:08 |
Message-ID: | 5339c9a90903170425u42091eaaid7726eae7eb2391b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
Hello,
I'm currently developing a program for centralizing the vehicle fleet GPS
information -http://openggd.sourceforge.net-, written in C++.
The database should have these requirements:
- The schema for this kind of data consists of several arguments -latitude,
longitude, time, speed. etc-, none of them is a text field.
- The database also should create a table for every truck -around 100
trucks-.
- There won't be more than 86400 * 365 rows per table -one GPS position
every second along one year-.
- There won't be more than 10 simultaneously read-only queries.
The question is: Which DBMS do you think is the best for this kind of
application? PostgreSQL or MySQL?
Thanks in advance
Juan Karlos.
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2009-03-17 11:36:52 | Re: PostgreSQL versus MySQL for GPS Data |
Previous Message | Dan Langille | 2009-03-17 00:23:24 | Preliminary PGCon 2009 schedule released |
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2009-03-17 11:36:52 | Re: PostgreSQL versus MySQL for GPS Data |
Previous Message | Enrico Pirozzi | 2009-03-17 11:16:20 | Records Number |