Christian wrote
> Ooopss...
> I didn't understand you wanted to rollback your transactions...
> I don't see anything else than code around your problem :
> The transaction should only be made when you are sure that it must be
commited.
> For example, your application should only perform an insert/commit when
your end user
> clics commit. If he clics rollback, nothing should be sent to the
database.
I'm not entirely sure how you would achieve this but anyway what do you do
about rollbacks caused for reasons other than and end user choosing not to
save their work. eg tablespace full - unable to extend temp segment by x
etc.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
Received on Fri Jun 28 2002 - 05:42:53 CDT
