C
ChUIMonster
Guest
If you imagine that you can write .NET code that makes multiple sequential calls to app servers to start database transactions and sub-transactions and then, later commit them or roll them back then you are not going to have success. If, on the other hand, the outline of transactions and sub-transactions that you showed is expected to occur within a single call to an app server then it would be within the normal 4gl capabilities. On 9/15/14, 10:34 AM, saiidcd@gmail.com wrote: RE: .Net and subtransactions Reply by saiidcd@gmail.com Thanks Tim. No we would not allow any user interaction to take place during our transactions but some of our business logic can be intricate and we may decide to roll back due to any of many reasons. I am trying to avoid the explicit delete as we are building a large large system and we are looking for something similar to the .Net TransactionScope or the way 4GL can roll back the enclosing transaction. Stop receiving emails on this subject. Flag this post as spam/abuse. -- Tom Bascom 603 396 4886 tom@greenfieldtech.com
Continue reading...
Continue reading...