Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: ewen fortune (ewen.fortunegmail.com)
Date: Wed Mar 18 2009 - 05:50:44 CDT
On Wed, Mar 18, 2009 at 11:14 AM, Juan Pereira
> 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
> - 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?
I think it depends on exactly what you want to do with the data. MySQL
has fairly poor support for spatial types but you can achieve a lot
just manipulating normal data types. Postgres (which i know nothing
about) appears to have better spatial support via "postgis"
In terms of data size you should not have a problem, I think you need
to look at how you are going to query the tables.
> Thanks in advance
> Juan Karlos.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql