In fact, it's only the first normal form: no repeating groups in an RDBS. Those need to be 'normalized away' to a separate table. And that, of course, has a foreign key referencing the entity it belongs to in the first table.
Another way to look at the same facts: it's a n:n-relationship between player and game. And n:n-relationships in a data model are represented by two 1:n-relationships in the relational model.
This is rather basic stuff. I expect a University course in relational database modelling to treat BCNF at least, and maybe even 4NF and 5NF. But that's a quite different story.
Hope this helps.
Kees
Hi, there's something I would like to keep track of, and my first thought was to make a database for it in Access (I used Access in conjunction with SQL to keep track of euchre stats a while back, so I'm rather familiar with database basics).
One table I'll be keeping track of will be session reports of various board games, and one item I'd like to keep track of is the players who played in that game. So, every game will have at least two players, but beyond that I don't know how many will play (euchre was easier; there were always four players).
Enough backstory; my question is, can databases (specifically, RDBS) handle lists as entries? That is, can one column in the table be called "players", and each entry has a list of entries from a "Player" table? Otherwise, can you suggest a better method of handling this data?
I took a course on RDBS in University, but I have no reason to believe that databases can do such a thing.

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic