agreeing with previous posts, try not to build tables to suit already known queries. You will have more in the future. store them as per rules of NORMALISATION and look up FOREIGN KEYS and INDEXING and CONSTRAINTS and FOREIGN KEYS
to refer to your previous post, everything between 'hobbies' and 'profile_views' (inclusive), as well as 'people_visted_my_profile' should be in a separate table like this (I think).
create table hobbies
( hobby_id int not null auto_increment
, user_id int not null
, hobby varchar(99)
, CONSTRAINT hobby_user_fk
foreign key (user_id)
references users(user_id) on delete cascade
assuming the main table with user_id is called 'users'
other tables for all those cols, as mentioned, should be of similar format. make sure data type of the parent key is the same as foreign key eg INT or VARCHAR(99) etc.
oh yeh, read up one 'one-to-one' relationships and 'one-to-many' relationships so you know which type of table to create ~ n-m or m-m.