|
When my clients have to make changes to their database, a MySQL transaction is commenced.
In time it is either committed or rolled back. Rollbacks happen in error scnarios and critically by user choice.
I am following Juval Lowy's method of implementing transactions with a view to picking up the ambient MySQL transaction being managed by the client.
So the client enteres a new row, WCF / MSMQ relays it to a service that calls another service and makes a database update - nothing is committed yet.
But the user has a change of mind - and hits Rollback rather than commit.
The row is rolled back on the client, but the remote update is committed.
Is what I am attempting techincally possible?
Ger
|
|
|
|
|
What you are after is technically possible - as long as the TransactionScope hasn't finished, the transaction can be rolled back by the user. Rather than the Lowy examples, I find them to miss out on some critical details and concentrate on less important bits, I would recommend this[^] article and this[^] blog post which cover it in a lot more depth.
|
|
|
|
|
Pete, we are on the same hymn sheet with Lowy - I printed those two articles off a couple of weeks back and read them then. I'll be lining them up beside my code when I get back to it this evening to see what I can flush out.
Ger
|
|
|
|