| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL versus MySQL for GPS Data |
| Date: | 2009-03-17 11:36:52 |
| Message-ID: | 20090317113652.GA3863@merkur.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
On Tue, Mar 17, 2009 at 12:25:08PM +0100, Juan Pereira wrote:
> 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 database also should create a table for every truck -around 100
> trucks-.
Why ? This smells like a design problem.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pedro Doria Meunier | 2009-03-17 11:43:44 | Re: PostgreSQL versus MySQL for GPS Data |
| Previous Message | Juan Pereira | 2009-03-17 11:25:08 | PostgreSQL versus MySQL for GPS Data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pedro Doria Meunier | 2009-03-17 11:43:44 | Re: PostgreSQL versus MySQL for GPS Data |
| Previous Message | Juan Pereira | 2009-03-17 11:25:08 | PostgreSQL versus MySQL for GPS Data |