| SitePoint Sponsor |
My friend insists on creating a new database for new data depending on what `round` it is. I've been trying to convince him to save the round data to another table and just link it instead of using the name in the table name. Any suggestions on what to tell him, why this is bad, ect?
I suggest you provide more information. As far as I can tell your friend is trying to build some sort of boxing statistics program. I dont know what you mean by rounds. Please elaborate on the overall scope of the project to put what your saying in prospective.
round data????
yeah, not enough info to offer specific advice, however, "new database" is hardly ever necessary, nor "new tables" either
i have seen many instances where people feel the need to split stuff off into new tables, ostensibly for the reason that "otherwise the queries take too long", and invariably it turns out that they have not understood the importance of proper indexing
Well given that everything breaks down to binary. I would assume roughly half of the data is round.
I'm sorry. I should have provided more information but was short on time. He is developing an application where matches are broken into `rounds` (basically like a two week cycle). Each round can have a number of matches between multiple teams. The application stores information about each persons stats during that match. The table structure I'm trying to get him off looks something like:
Name of each new column, with the variables in bold:
statsround_match_id
with columns like so:
person, team, time played, ect
Example table names look like:
stats1_1
stats1_2
stats1_3
stats2_1
stats2_2
stats2_3
and so on.
that's sad
ask him to write the sql to show summary win percentages for all teams that played in the first two rounds
I was also thinking querys which involve all players, like total time played, ect.
Heh, I asked him these questions and he responded with something along the lines of "I don't know, I havn't got that far yet."
Posting Permissions
Bookmarks