Subject | Re: How to avoid automatic foreign key index |
---|---|
Author | Christian Kaufmann |
Post date | 2008-03-16T15:59:56Z |
> See above. But I must say it's a bit puzzling why the samehttp://www.swimrankings.net/index.php?page=resultDetail&id=9600087
> SWIMRESULT master would involve different distances in the
> detail...are the races handicapped on distance? Just curious...
Here you see a typical result from a swim meet. There is always a
final time, which I save in the SWIMRESULT record as well. But every
swimresult has intermediate times which are interesting for coaches
and are displayed on detail view.
I saw having a SPLITID as primary key in the table SPLIT just as
unnecessary overhead since if I manipulate split times, all times for
one result are loaded to a grid and if there are changes, I delete all
existing splits and insert the new ones as new records.
Another solution I'm thinking of now is adding triggers for update and
delete in table SWIMRESULT and update the records in SPLIT there. This
probably doesn't fit in your puristic view either, because this allows
to have inconsistent data in my database.
cu Christian