I have a bunch of similar data for profiles, like: name, pass, id, url, date, ldate, des, a, gen. Should I store the data in one table, with column names refering to the data it contains or should I create a table in the database for each user? Thanks. ~imozeb
That depends on how you planned your application, but it looks to me that the first choice is wiser... you can easily find members who: * singed at a specific date range * using the same password * who are male or female etc...
Okay, thanks. Just one more question. Is there a max amount of data I can store in one table or is this just the max data I can store in the entire database?
it depends on how you developed your application. make it sure to make your design normalize for you to easily handle your data. try to study database normalization.
see , as per fields you specified, batter will be to use one table, as you can get retrieval of all users at a time. but here fields like Email ID, user ID and contact number should me unique. so you put constrain on these fields. and further more you can use primary key and foreign key constrain if you need to co relate any table with this one in future . thanks. best of luck.