June 2, 2010 at 9:46 pm
Hi All,
Here is my problem,I have to create an application where any changes made to a table
goes through an approval process, if approved we keep the history and make the changed row the current row in the table , if not
we discard the change and use the most recent row in the table as the current row.
It sounded easy to me at first but when I considered the fact that I have to deal with forty tables including association tables, things
started to get complicated, If I change a row in one table (say table1) and goes through the approval process, in the mean time the rows in other tables not going through the change
process but related to the “table1” are pointing to a row that’s not going through the approval process(previous row). Then another issue comes up as changing more than one table at a time.
Am I making it too complicated or is it complicated in reality?
Thanks for your time
Ash
June 2, 2010 at 10:32 pm
Personally this is something I would do on the application side. You would need a separate set of tables to hold the data you need for your application to function, but I wouldn't commit any changes to the existing live tables you have until whatever business process you need to approve the change has been completed.
Obviously there are a lot of nuances to this scenario, so without knowing significantly more about your specific situation that would be my two cents.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply