Re: Black Karma Hockey Manager
Posted: Mon Feb 29, 2016 8:47 am
So Ive started work on the game again. Im graduated now so everything should be okay, I have my passion back
Ive been playing around with Editors, because of course I have, and ive noticed weaknesses in database designs. Basically what I want to do is build databased out of constituent parts. IE if you create the British Columbia Professional Hockey league you create the 15 teams, and give those teams their 25 players. You usually would need to re-create those teams in every database you would want to use them in order to make sure they're compatible or else worry about version control and stuff like that. But in this design if you make a change to a team like Langley and make their jerseys Yellow instead of Black then that change would carry over to every database that uses that Langley team. So if you had this one league of teams in BC and you also had say a Database that separated Cascadia, Quebec, Ontario, the Maritimes, Texas, etc into their own countries you could plop them into that database and if you had a database where the US Anexes Canada you could plop them into that database, and if you wanted to use it in the default database you could plop it into that as well, so that when you make a change to the Langley team it makes the change to all 3 databases automatically so you don't have to worry about duplicating work (Which is a big problem in stuff like this)
Ive been playing around with Editors, because of course I have, and ive noticed weaknesses in database designs. Basically what I want to do is build databased out of constituent parts. IE if you create the British Columbia Professional Hockey league you create the 15 teams, and give those teams their 25 players. You usually would need to re-create those teams in every database you would want to use them in order to make sure they're compatible or else worry about version control and stuff like that. But in this design if you make a change to a team like Langley and make their jerseys Yellow instead of Black then that change would carry over to every database that uses that Langley team. So if you had this one league of teams in BC and you also had say a Database that separated Cascadia, Quebec, Ontario, the Maritimes, Texas, etc into their own countries you could plop them into that database and if you had a database where the US Anexes Canada you could plop them into that database, and if you wanted to use it in the default database you could plop it into that as well, so that when you make a change to the Langley team it makes the change to all 3 databases automatically so you don't have to worry about duplicating work (Which is a big problem in stuff like this)