2
Separate table is a good idea. But about "creating records in it as soon as product request is created", I am not so sure about.
My suggestion:
t1 - product request : insert record as soon as product request is created.
t2 - product request approvals : a set of 10 records which indicate which approvals must be obtained. Note that this table DOES NOT have record for actual approval received.
t3 - product request approvals received : again a set of 10 records which indicate that approvals actually received. There may be 0 records at the beginning but insert each record as approval is received. This has who approved, when approved, comments, etc.
t4 - Optional - auditing of t3 table. In this log each change in t3 (insert update delete of t3) Who gave approval and then revoked it, etc.
The benefit of above approach is you can select records from t2 left outer join with t3 and know pending approvals. I am sure you will need it some time. Note that t2 is just a template table. This approach protects you from increase / decrease in number of approvals.
0 Thanks!
Feel free to ping for any other question(s) you have face in the process.
0 Thank you Nitin. The missing link for me was the Left Outer Join and inserting after approval. You have cleared things up.
9 years ago I was just getting started as an independent consultant and was hopeful to pick up as a programmer. Consulting opportunities directed me in other areas, BA and Systems admin. I now have the fortune to implement small projects that are mostly data capture and reporting. A great opportunity to learn.
Thanks again
0 Somehow it surprises me that you ask your first question after full 9 years after becoming member of this forum.