Deducting data vs saving it explicitly
-
Hi, I'm kind of confused on this. If I have data on tables, and I'd like to know something which is deducted from that data, but requires several tables and calculations.. should I make that "something" an explicit data (table, attribute, who knows)? For example: I have a table of "goals", "matches" and "teams" of some football tournament. and I want to know the number of win matches of some team, then I would have to calculate them by comparing the number of goals, etc etc. But if Id put a column of "WonGames" in the table of teams, then this wouldnt be needed What is the correct approach? Thanks
-
Hi, I'm kind of confused on this. If I have data on tables, and I'd like to know something which is deducted from that data, but requires several tables and calculations.. should I make that "something" an explicit data (table, attribute, who knows)? For example: I have a table of "goals", "matches" and "teams" of some football tournament. and I want to know the number of win matches of some team, then I would have to calculate them by comparing the number of goals, etc etc. But if Id put a column of "WonGames" in the table of teams, then this wouldnt be needed What is the correct approach? Thanks
Alivemau5 wrote:
deducted
Deduced? With some such things, you might want to do both; have a detailed transaction table and a summary table.
-
Hi, I'm kind of confused on this. If I have data on tables, and I'd like to know something which is deducted from that data, but requires several tables and calculations.. should I make that "something" an explicit data (table, attribute, who knows)? For example: I have a table of "goals", "matches" and "teams" of some football tournament. and I want to know the number of win matches of some team, then I would have to calculate them by comparing the number of goals, etc etc. But if Id put a column of "WonGames" in the table of teams, then this wouldnt be needed What is the correct approach? Thanks
continuuing from PIEBALDconsult, this is why a good deal of time usually goes into data analysis (and sometimes even then it takes multiple evolutions to get it right) If dynamically recalculating the result(s) each time starts getting onerous or you need them elsewehere and dont wish to use temp tables for example, you may need to maintain a transaction table as he suggests 'g'
-
Hi, I'm kind of confused on this. If I have data on tables, and I'd like to know something which is deducted from that data, but requires several tables and calculations.. should I make that "something" an explicit data (table, attribute, who knows)? For example: I have a table of "goals", "matches" and "teams" of some football tournament. and I want to know the number of win matches of some team, then I would have to calculate them by comparing the number of goals, etc etc. But if Id put a column of "WonGames" in the table of teams, then this wouldnt be needed What is the correct approach? Thanks
P.S.
Alivemau5 wrote:
put a column of "WonGames" in the table of teams
Then I think you could only track one season at a time; you may need a season table -- which might be a good place to store such summary data.
-
Hi, I'm kind of confused on this. If I have data on tables, and I'd like to know something which is deducted from that data, but requires several tables and calculations.. should I make that "something" an explicit data (table, attribute, who knows)? For example: I have a table of "goals", "matches" and "teams" of some football tournament. and I want to know the number of win matches of some team, then I would have to calculate them by comparing the number of goals, etc etc. But if Id put a column of "WonGames" in the table of teams, then this wouldnt be needed What is the correct approach? Thanks