I strongly suggest that you make a separate table for the manager <-> team
relationship, so you can keep a history. Put a date-stamp in there. This might
come in handy as you get further into your design.
I ran into this problem when one of our sales reps moved from one office to
another, and took their sales history with them! That was a mess to
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
Web site: www.the-infoshop.com
>From: Neil Tompkins [mailto:neil.tompkins@stripped]
>Sent: Tuesday, August 31, 2010 3:48 PM
>Subject: Database design help
>I've a soccer application consisting of managers, teams players and
>fixtures/results. Basically each manager will get points for each game
>which will depend on the result.
>What would be the best table design bearing in mind that a manager can
>move to a different club.
>My thought was to have a field in the fixtures/results table for the
>manager points but i think that I will also need a users field so that
>I can remember which points belong to which manager.
>Is this the correct approach??
>MySQL General Mailing List
>For list archives: http://lists.mysql.com/mysql
>To unsubscribe: http://lists.mysql.com/mysql?unsub=1