C
ChUIMonster
Guest
.NET or not has nothing to do with how transactions work. Generally speaking I would expect that "some business logic" would be executed *before* you decided to commit a transaction to the database. Doing so in the middle of a database transaction opens the door to problems with consistency, concurrency, record locks and so forth. And if "business logic" includes user activity (even something like an "are you sure?" button) you're really asking for trouble. On 9/15/14, 9:59 AM, saiidcd@gmail.com wrote: .Net and subtransactions Thread created by saiidcd@gmail.com Hello everyone, We are looking at developing a .Net project that accesses a progress database. We have identified a possible problem area in the event of multiple transactions. The following highlights the situation with some pseudo .Net code: Start Transaction TA Start Subtransaction T1 Create Customer Commit Subtransaction T1 Perform some business logic Start Subtransaction T2 Create Order Commit Subtransaction T2 Start Subtransaction T3 Create OrderLine If create OrderLine failed then roll back transaction TA including T1 and T2 Commit Subtransaction T3 If some condition is detected then roll back transaction TA including T1, T2 and T3 CommitTransaction TA Of course the tables involved in this example are for illustration purposes only. The question is, can we do this from .Net code? and how? We are willing to have the .Net code call into a "progress based data access" layer. Stop receiving emails on this subject. Flag this post as spam/abuse. -- Tom Bascom 603 396 4886 tom@greenfieldtech.com
Continue reading...
Continue reading...