Page 1 of 1
How many rows is too many rows
Posted: Sat Sep 09, 2006 7:57 pm
by GeXus
Say I have a bunch of data that is only a one to one relationship.. and will never change. Would it make sense to store all of that in one table? Such as a users table... it could potentially have 50+ columns.
Posted: Sat Sep 09, 2006 8:23 pm
by feyd
If all the columns will be accessed frequently, then keeping them together could be considered a good idea. But if not, then there is a potential to break the table apart a bit. Are there large columns such as TEXT or BLOB? Then there may be potential of breaking those out as well, depending on their use and such.
Posted: Sat Sep 09, 2006 8:33 pm
by GeXus
Alot of the columns will be varchar and text... and they will be accessed frequently... The problem is just having a logical way to break them up.. since they really all pertain to the same thing.
Posted: Sat Sep 09, 2006 8:36 pm
by feyd
If you care to explain them all, we may be able to come up with common themes to break them apart into.
Posted: Sat Sep 09, 2006 8:39 pm
by GeXus
Thanks, I think i've actually got it.. basically the information will all be collected from 3 seperate pages, each page is sort of like a subject.. so that works perfect to break them up that way...