Gayner Posted August 21, 2009 Share Posted August 21, 2009 $DB->query("SELECT * FROM ibf_members"); I have over let's say 50 Field names in my IBF_members table. So should call what i need let's say about "25-30 field names" seperately, or use the * so it is quicker ? Which way is more artificial? and less on the database and performance wise? Quote Link to comment Share on other sites More sharing options...
Alex Posted August 21, 2009 Share Posted August 21, 2009 Depending on how many rows you're calling there shouldn't be much of a performance difference. Quote Link to comment Share on other sites More sharing options...
.josh Posted August 21, 2009 Share Posted August 21, 2009 I think the better thing for you to do would probably be to look into breaking that 50 column table down into several tables... Quote Link to comment Share on other sites More sharing options...
Gayner Posted August 21, 2009 Author Share Posted August 21, 2009 Depending on how many rows you're calling there shouldn't be much of a performance difference. Actually i counte.d. about 150 Field names... in that 1 table. I only use about 30 on the profile page, should i call them out seperately? I Think i should call them separately, lol Quote Link to comment Share on other sites More sharing options...
.josh Posted August 21, 2009 Share Posted August 21, 2009 okay for real, 150 columns in a table...something is very wrong with that picture. Quote Link to comment Share on other sites More sharing options...
Gayner Posted August 21, 2009 Author Share Posted August 21, 2009 okay for real, 150 columns in a table...something is very wrong with that picture. Ok, look, i'l giv u a screenshot tell me if this is bad, im only using like 25field names anyway so u think i should call separately yes or no ? Quote Link to comment Share on other sites More sharing options...
spelltwister Posted August 21, 2009 Share Posted August 21, 2009 I would say, yeah, that's probably not the greatest arrangement of data. You can't think of a way to break it into logical units? For example, if you have 25 or so of the columns that you frequently use, why not put them together. Also, fields that are frequently blank, perhaps those should be somewhere else? Think of it this way; if i have 1,000,000 users, but only 300 of them have some field set, why have room set for all of them? Quote Link to comment Share on other sites More sharing options...
Gayner Posted August 21, 2009 Author Share Posted August 21, 2009 I would say, yeah, that's probably not the greatest arrangement of data. You can't think of a way to break it into logical units? For example, if you have 25 or so of the columns that you frequently use, why not put them together. Also, fields that are frequently blank, perhaps those should be somewhere else? Think of it this way; if i have 1,000,000 users, but only 300 of them have some field set, why have room set for all of them? Ic well im glad I made this topic, no wonder my hosting has server status in red all the time, LOL Because each time a profile is view it's mysqling over 120 extra fields that means nothing, that could be 4-500 more people.. lol Quote Link to comment 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.