This is a database I made for a project, any feedback is appreciated. Is setting up the handPlayed and Bet tables like this bad design? I rarely see designs set up like this. Is there a better way to do it without sacrificing too much performance (which is important for this application). thanks.

db_relationships.GIF

I would probably make the Bet table a child of the HandPlayed table.
It's PK would be HandNum, PlayerNum, and BetNum. (BetNum would begin with 1, and increment for each Player/Bet number.) HandNum and PlayerNum would be fk's to HandPlayed.

PlayerNum 1, HandNum 1, BetNum 1, type, amount...
PlayerNum 2, HandNum 1, BetNum 1, type, amount...
...
PlayerNum 1, HandNum 1, BetNum 2, type, amount...
PlayerNum 2, HandNum 1, BetNum 2, type=fold, 0, ...

I think that this probably models the game better than two, discrete intersection tables.

thanks for the help.

will this change effect the performance? for better or worse? probably not?

does my original design break any basic normalization rules? Its in 3rd normal form - right?

sorry, I'm getting burnt out on this, can't think straight anymore

i noticed holecardrank is dependent on holdcards, so this is not in 3nf. this is not really important, I'll probably remove the holecards attribute, i don't use it anymore.

I can't decide if i want to change to the alternative design or not. What would be the difference if I want to do a query like, select all bets for a player?