table design issue
I have an web application. User wants to do the following task every year in the web interface.
(i) save / submit data any number of times for multiple records in a given year in the UI.
(ii) approve all records once in a year in the UI..... once approved records user can not modify.
Should I make two tables ? one for save/submit for multiple records entered by user and other for approve user ?
Should I make one table ? save/submit/approve for multiple records all in one table ?
how do I design my table to do this ?
i would use two tables, where the "approved" table has one row, one column
i like to use a column in "approved" with 0 or 1 in the first table.it be easier to query about.
Originally Posted by r937