Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

hunterhawley's avatar

Variable Class Names or Secondary Table?

Hey y'all!

I have a table, 'basketball_game_events', and it is full of, you guessed it, all the things that happened during basketball games (assists, rebounds, etc.). The thing is, some of these events are shot types. Normally, a game event only needs 6 columns to be complete. However, there are 3 additional columns needed if we are talking about a type of shot (2 pointer made/missed, 3 pointed made/missed, you get the picture).

My question, would you all recommend breaking those last three columns off into a different table? On the one hand, it would clean my table up quite a bit and save me from seeing tons of NULL when it isn't needed. On the other, if I did break it off, I would have to do a lot more joins with my queries, and I would still have to have a reference column full of NULLs for none-shots.

I know this is probably largely opinion-based, but... I would love some opinions haha

0 likes
1 reply
mehaneef's avatar

I think you should break three columns to different table. It will quite simple to manage it.

Please or to participate in this conversation.