|
I’m honestly asking, because 42+ fields in the same table and you’re not calling bad practice?.?.?.?.? so much for professional level dev
you still clearly do not understand that you are normalising them for the sake of normalisation. stop and think for one second about the queries you are writing: player save, player load.
in both of these queries you end up inserting/selecting all of the fields from all of these tables. that means each time a player is loaded you're joining on these 5 tables, and each time a player is saved you're writing 5 separate insert statements.
by denormalising, you would avoid all of the joins and consolidate the inserts into a single insert statement.
i have close to 5 years experience as a professional software developer, u?
can you actually explain why you think massive tables are bad? what performance gain are you getting out of splitting them? you certainly aren't improving the amount of storage space it takes to store the data.
literally the intro to database design class here tells you exactly the same things scu11 has posted multiple times throughout the thread (i.e. don't do exactly what you're doing - normalizing just to do it, designing your schema before thinking about your data and how you want to query it)
I don't know how you've made it 7 years in industry without knowing these things that you'd pick up 1st year CS, all while acting incredibly arrogant about it
it's one thing to be wrong; that's fine, everybody is, and often, but it's another to plug your ears and keep repeating the same shit while acting like everyone else trying to help you is an idiot
Hey man, be careful to not pop his inflated ego. Easier, for him, to continue on a trail of denial and deflection than it is to admit fault: He'd rather be right, even if it means being wrong.
There's no point in continuing a discussion with someone who's arguing solely for the sake of being right.
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |