![]() ![]() I'm still not sure if this is entirely a bad thing - the alternative, having a single set of tables which had properties on it that not all sports would use, might have on its own been unwieldy as well. ![]() it goes on for say 5-10 tables across 4 or 5 sports. each table might have a few properties that the other one doesn't, and several that are shared. I have something like NBA_Game, NFL_Game, NBA_Team,NFL_Team, etc. The result is duplicated schema in several of the tables, and so duplicated interfaces to the database (e.g. Each sport has a different Schema to which we receive data from our vendor.īecause there wasn't enough time (client demands) to do upfront analysis of the data feeds to determine commonalities, I hedged my bet and took the 'safe bet' and made individual separate tables for each sport instead of one set of tables that all sports used. Our data source of course does not give us each piece of data in the same schema. Each sport has very similar concepts - Teams, Schedules, Injuries, Player info. ![]() We can handle NBA,NHL,MLB,NFL for example. I am creating a Sports information application which can handle multiple sports. I am working on a project where at some point, I needed to make a decision on whether or not, in the database, I should have a single table with multiple columns that not every record uses, or multiple tables with duplicated schema. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |