I'm creating a blogging site that anyone can sign up and be an author for. I want each author to have their own public profile. My main question is; would it be better practice to have a separate profile table that contains fields that would be specific to only the profile page, or should I just add those profile fields to a general users table as this example shows:
CREATE TABLE IF NOT EXISTS `users` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(255) NOT NULL, `first_name` varchar(255) NOT NULL, `last_name` varchar(255) NOT NULL, `email` varchar(255) NOT NULL, `password` varchar(32) NOT NULL, `sign_up_date` date NOT NULL, `activated` enum('0','1') NOT NULL, `admin` int(1) 0 , `bio` text NOT NULL, `profile_pic` text NOT NULL, PRIMARY KEY (`id`) )
bio and profile_pic are both profile fields in this case. This is also just an example, I plan to have more fields for general user stuff and not to many more for the public profile, but that could change as I move further into development.
Sorry if this an opinion and not a best practice question. I'm new to Database architecture.