php_guest Posted March 4, 2010 Share Posted March 4, 2010 The below is my table structure. Do you think I should create 2 tables to have less columns in 1 table? I was thinking to separate registration and account related data (password, registrationemail , date_registered, profileviews, ...) to another table. But does it make any difference in performance at all since each field will have only 1 data? userid | password | registrationemail | level_access | date_registered | Random_key | temp_pass | active | profileviews | firstname | lastname | phone | address | city | postcode | country | birthday | currentstatus | currentcompany | image | academictitle | academicdegree | workingtitle | companyname | profilecompleted | description | twitterid | facebookid | www | allownotifications | allowprivacy | allowcontact tnx! Quote Link to comment https://forums.phpfreaks.com/topic/194188-table-structure-too-many-columns/ Share on other sites More sharing options...
Dennis1986 Posted March 4, 2010 Share Posted March 4, 2010 No problem at all. In fact you're only making it worse by splitting it into seperate tables. Hell, go add in 50 more fields if you like Edit: On a sidenote... Make sure you are using prober field types for each field depending on what kind of data you are storing. This makes the difference in performance and size. Quote Link to comment https://forums.phpfreaks.com/topic/194188-table-structure-too-many-columns/#findComment-1021703 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.