I noticed while testing that if pooling is set to spInternal and RollbackOnDisconnect is set to True that the LogOff procedure doesn't perform the rollback. If I set the pooling to spNone then LogOff does perform the rollback.
That sounds backwards to me. I would think that it is imperative that a rollback be performed if you are using a pooled connection since you don't want the next guy that uses your session to commit data that you changed.
1. Any ideas as to why this is?
2. Would it hurt us to remove the "not Shared" check prior to the Rollback in the LogOff procedure in Oracle.pas?
Thanks,
Duane
That sounds backwards to me. I would think that it is imperative that a rollback be performed if you are using a pooled connection since you don't want the next guy that uses your session to commit data that you changed.
1. Any ideas as to why this is?
2. Would it hurt us to remove the "not Shared" check prior to the Rollback in the LogOff procedure in Oracle.pas?
Thanks,
Duane