once you are loged in it only say's there are three links visible
| List Players | List Fixtures | Team selection | (personally my design has placed the team selection link within the fixture.... but don't think it has to be 100% same?)
as for the Team selection and what it must do... well to me it is only logical that it must give you the ability to select a team...
from a list of all the players, and allocate it to a specific fixture...
team = subset of all players
every fixture has ability to have a different team selected.
Registered: 14 years ago
Use some logic...write it down on a piece of paper using your own words. Then think how you will code it.
selection id is e.g. 1 which points at the unique identifier for that row (the primary key, which is automatically created). Fixture id is drawn from the fixture table. The rest of the columns in that row consists of the player id's..
Here is a typical row
sid = 1
fid = 3
fullback = 15
wing = 8
centre = 4
...and so foth
So to generate the list you need to get the fixture from fixture table using fid 3 (as you inserted it)
Get player name, surname from player table for fullback, using player id 15
I think its important to understand what the selection table is all about, initially i had a for example in column Bowler, i had a name and surname, haha!
Now i realized that after each line in selection is actually a team, and the position columns have relationship with playerid.
Sir, will it be ok if we put in primary key, foreign key relationships between each of the columns such as Bowler, Batsman etc which are the foreign keys in the selection table and the Player table which has the primary key?