All,
What's the accepted best practice for persisting data? Commit by the
PL/SQL or commit by the caller (C#, Java, VB, etc.). I believe that
if the caller starts a transaction and calls PL/SQL that contains
commit/rollback that the XA Manager throws an exception. Since I
can't predict what the caller of my PL/SQL could do, I'm leaning
towards having the caller handle the transaction as a precondition of
calling into the database layer.
Comments are appreciated.
Matt Houseman