The-Last-Escape Posted May 1, 2007 Share Posted May 1, 2007 i am designing a member login program and am having problems working out how to lay out the DB. i have a maintenance option, where they fill in a form and it adds it to a db, would it be best to have 1 maintenance table with all of the members queries etc in it or a seperate table for each member? but i will need to be able to reply to the queries and have them stored too. so should i use a maintenance post table and then have a replies table, or should i have a table that has all the members and all of their posts in it? Quote Link to comment Share on other sites More sharing options...
tauchai83 Posted May 2, 2007 Share Posted May 2, 2007 it is up to you. For me, i will us one table. If your application is small, then you can have many table as you like. When the application is big, normally i try to reduce the number of tables. It doesn't mean i ignore the NORMALIZATION process. It is up to you. 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.