Optimistic concurrency control in master-detail

  • Thread starter Thread starter Ivar Zapata
  • Start date Start date
I

Ivar Zapata

Suppose:

1) Only the "Master" table has a timestamp column
2) Use of datasets
3) A deleted or modified "Detail" row update should check first the
"Master" row's timestamp value to see if somebody else modified it.

The problem is that if the "Detail" row is deleted there is no way to
know which is the parent row.

Any ideas?
 
Hello,

for this kind of problems, it depends on the server memory, and the
database engine.
Why do you need to delete the row? you can add a "flag" column marking it
as deleted; and run an "update" service every while that deletes flagged
rows; depending on the time you need to have access to that specific row.
Please let me know if I misunderstood your question.
If you have more questions regarding this issue, don't hesitate to reply
back.

Regards,
Rami Saad
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC
 
Back
Top