Im size 7-9ish

Looks nice Ryan, can’t wait to see some more pages.

Ok well the cloning of teams wouldn’t change either way, you would still be able to do it as thats done on the php side of things, and I can see where this will be handly now. It may be a little tasking on visiting teams if this system is used however as all the tops have to entered first.

Heres what ill do, I will add a new table with tops, the team name colour and description, and also the option to have a photo or picture, When creating a team you can choose the top, if a top isn’t there you’ll have to add it (this is where i could see the problems with visiting teams or national/international events)

Sound good?

This situation is dunedin specific because we share tops, But the teams are not the same!, just because the name is Beasts does not mean that they are the same team , if they were the same team they would have the same people. so creating and reusing the Beasts team would be silly as its not really the beasts team.

Good input once again Kyle ” title=”Cheesy” /> now its time for me to explain a few things

Having a seperate table for position covers the multiple positions thing, so for each position they play on a team etc another entry is added to players_positions. By ticking 1 or more boxes it will add one or more entry’s stating that users ID the team they will be playing that position for “if applicable” and the position.

With finances I was not sure if there would be a need for it to be linked back to a tournament or game as some finance items may not be related to one, this is why each one has a “Description”. But I see how it will be helpful, I will add a link to tournaments.

A player can be in any number of teams. Players are placed into teams before the tournament by organizers or by choice (However things are run for that tournament), so there is no limit as to how many times a player is entered.

I agree with the extra email contacts, I will add that also.

Teams do not need the manager, coach or ass. coach and if its changed its changed for that “Team” so each entry of a team is changed.

“Time” referees to a UNIX timestamp, it has no specific format.

Venue is a good idea, I will add it.

I had a discussion with Ryan about the competition thing, the reason why I have the option to add teams directly to a competition is because not all competitions will have more than one devision, in the case that a competition only had one devision the organizer entering the competition would be required to specify a devision for a tournament with no divisions?

Instead it has the option to have a devision less competition or one with devisions.

If a competition has more than one devision it will ignore the “completions_teams” table completely and look in “divisions_teams” hence the double up there.

• period1_start
• period2_start
• period3_start

These are for another underlining possiblilty of the program, To speed things along for the scorers I’m looking at making a scoring program that will work with the database to make there lives easier. The period starts would allow a detailed time line of how the game went for players to view after the game.

[quote:van2xuab]
I don’t understand why you need this one either. It’s just a linkage, why not have a one-to-many relationship between the table before and teams? I’m no SQL expert though, so maybe you just need to. And, that’s not how you spell division. [/quote:van2xuab]

Good question, it comes down to efficiently and size of MySQL and the database, yes thats the way about 80% of people who have not worked with any type of SQL database for a very very long time would do it. But… By adding 2 extra tables that arn’t going to be used every time you are adding to the size of each entry. By using a separate table assists are only entered when they happen instead of when they don’t happen also. ( Things shouldn’t be left blank as a rule of thumb, but sometimes its unavoidable ).

[quote:van2xuab]If you have ‘type’ you shouldn’t need to enter minutes. It should look it up from a table, I can’t think that we’d want people manually entering how long penalties are. Minor, double minor, major, game etc are all fixed. [/quote:van2xuab]

I see what you mean, but people would not have to enter it manually, I was thinking here it would just be added by the type of penalty any way. So I suppose there isn’t a need for time but instead a new table for penalties and there times.

Did not know about the period thing, will add something now.
Also the time thing is another fancy thing that would be included in the scoring system, when they clicked for a shot at the net it would record the time as well with no extra effort for a detailed time line of the game ” title=”Cheesy” />

If manually entered the times would be unneeded

Hope this clears some things up.[/quote]

Mmm well so far I’ve set it up for tournament’s and finances, I’m going to be working on stats today then Ill start building a front end to this mammoth.

Edit: for those interested in database structure, heres my first draft, I am now entering it in as a MySQL database with the correct datatypes etc.

Database Scheme

Table “users”
• user_id (Auto increment)
• player_id
• username
• password (SHA1) VARCHAR (40)
• email
• type

Table “players”
• player_id (Auto increment)
• first_name
• last_name
• picture?
• experience (Highest level played)
• played_time (Length of time played)
• registered
• management_only
• date_of_birth

Table “players_positions”
• player_id
• team_id
• position

Tables “players_finances”
• player_id
• type (topay, payed)
• description
• amount
• time

Table “players_hired_gear”
• player_id
• item

Table “players_addresses”
• player_id
• street
• suburb
• city
• country
• post_code
• description

Table “players_phonenumbers”
• player_id
• type
• description
• area_code
• number

Table “players_teams”
• player_id
• team_id
• number

Table “teams”
• team_id (Auto increment)
• name
• description
• color
• alternate_color
• manager
• coach
• assistant_coach

Table “competitions”
• competition_id (Auto increment)
• name
• description
• start_time

Table “competitions_teams”
• competition _id
• team_id

Table “devisions”
• devision_id (Auto increment)
• competition_id
• name
• description

Table “devisions_teams”
• devision_id
• team_id

Table “games”
• game_id (Auto)
• competition_id
• devision_id
• description
• team1_id
• team2_id
• scheduled_start
• period1_start
• period2_start
• period3_start

Table “goals”
• goal_id
• game_id
• player_id
• team_id
• time

Table “goals_assisted”
• goal_id
• player_id

Table “penalties”
• penalty_id
• game_id
• player_id
• team_id
• type
• description
• minutes
• time

Table “shots”
• shot_id
• game_id
• player_id
• team_id
• time

This will change slightly as I notice things that need to be added or removed, it can have features added to it as we need them also

In terms of difficulty I would rate something like that 1/10 lol, its basic input output of database, List the features you want in our own home brew scoring page and ill get it done in my spare time.

Be imaginative, what ever you can dream I can build ” title=”Cheesy” />