Ed Leafe wrote: > On Feb 13, 2007, at 6:21 PM, Uwe Grauer wrote: > >> Running different functionality or just forms in different >> transactions >> isn't esoteric usage at all! > > I can see that in the situation where you are working in a > pessimistic transaction locking scheme, where a transaction is begun > at the beginning of editing, rather than at the point of saving. In > optimistic locking designs, the chance of two transactions occurring > simultaneously is small, and most RDBMSs have a queuing system to > handle those cases. > > I can't see messing with the shared connection pool design right > now. Just keep in mind that you can grab the connection definition > from the app, and use it to create as many connections as you wish; > you just can't do it using app.getConnectionByName(). > > -- Ed Leafe
Yes, sometime you want to serialize things or just want to make sure things are isolated from other operations. I will see if i can establish something without messing with the things we have now. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
