Too many MySQL tables?

[BigThinker]

I would personally have two tables. One for all the species information and one for all the necessary data that needs to be saved per pet. I don't know if you combined the two but I'd be careful if you did. A simple INNER JOIN query would be able to join the two tables together if you needed any information from both. A lot of columns could impact performance, it's harder to manage, and it isn't really good normalization practice.

@judda correct me if I'm wrong. ^.^

Off the top of my head, I think there are two tables that are for pets. One for all the basic info and one for gaming info.. Hmm.. My entire site needs recoding because of me anyway but I'm in the process of organizing and such so I'll definitely keep the tables in mind.

[Chris]

I would personally have two tables. One for all the species information and one for all the necessary data that needs to be saved per pet.

That's sounds reasonable (BTW, I'm from the anti-join order and while I love to denormalize I find that in the example you gave join is the lesser evil ).

[Gabby]

That's sounds reasonable (BTW, I'm from the anti-join order and while I love to denormalize I find that in the example you gave join is the lesser evil ).

That means so much to me! I really appreciated this comment. <3 Thank you so much.