Kids will have their wish list that’s another table that we wanna reference. Then of course do we have the name of the toys in the table, or simple reference “Toys” table.
Also need an address table as some kids get Santa gifts at more than one house…
I didn’t even consider incorporating toy distribution… At what levels should kids get a small gift(a toy or game) vs a large gift(bike, game system etc).
In a real world scenario I would probably spilt this between 2 databases… One for kids (“with a nice score of 2 you get a toy of value 4 or less”) and one for toys (“the toys available with a value less than 4 are…”)
Ooh this is actually a good learning example.
Kids will have their wish list that’s another table that we wanna reference. Then of course do we have the name of the toys in the table, or simple reference “Toys” table.
Also need an address table as some kids get Santa gifts at more than one house…
I didn’t even consider incorporating toy distribution… At what levels should kids get a small gift(a toy or game) vs a large gift(bike, game system etc).
In a real world scenario I would probably spilt this between 2 databases… One for kids (“with a nice score of 2 you get a toy of value 4 or less”) and one for toys (“the toys available with a value less than 4 are…”)
Gonna need a whole auto converter thing to make sure that requests for “ps” “play station” and “new play station” all get converted to same thing!
Yeah… Which is 100x more complicated cause Microsoft has no idea how to name consoles