On Fri, 28 Apr 2000 [EMAIL PROTECTED] wrote:
> Although all in all I'd choose Postgresql too, it might be interesting to
> point out that in terms of performance, MySql delivers about 10 times
> quicker, which I do not know if it is something to be taken into account.
I think that the fist thing to do is put up a good database schema.
I'm using now Postgresql for a business application, and also have
set up another application that uses MySQL.
Postgres is anyway reasonably fast, and is more powerful, especially
having triggers and stored procedures could simplify the life a lot.
You can put the checking into the database and create a lot of different
frontends with less problem than a simpler database, having the
consistency check done by the front-end.
The big problem I see is that a contest logging program has different
requirements respect a standard logging program. In fact a QSO contest
is a different entity respect a normal QSO [1]. And you have different
rules for different contest.
Starting a requisite analisys is a good start.
Mike
[1] You model the same thing in a different manner. In a contest you
are interested in IW1CFL 59042 JN35RD. A standard QSO you are interested
in IW1CFL 59 Mike Givoletto 2W 144.340.
