I want to design a database for a "poker" application. It's to help
keep track of how my opponents played.

I want to store every hand a player has showndown in the database, so
for example player "bigfish" he could have 1000's of hands, of which
there could be duplicates, ie: he could of shown down AA more than
once. I plan to store the action(what happened on flop/turn/river) for
each hand, so I have to allow for duplicates.

ie: bigfile could of played AA and bet it on flop, bet it on turn,
checked on river. -- i want to store all this.
He could have another hand, with AA and bet on flop, checked on turn,
bet on river etc.


Anyone have any idea how i can go about desiging a database for this?

ZER0K3WL wrote:

Just make sure your table has an AutoNumber field set as the primary key.
Then you can have your PlayerName, Action, CardsShown, CardsDown, etc.
This will allow duplicate records while still having a unique identifier.
If you don't need the unique identifier, you may get away with not even
defining a primary key.