Hello all,
I'm new to the list and had a question. I know the default behavior for
savepoints (or any transactions) is that if they have not been committed, if
the program crashes, they are lost. Is there any way to have them committed by
default? Basically I *only* want the transaction rolled
Is there any way to have them committed by
default? Basically I *only* want the transaction rolled back in case of an
explicit rollback statement, not due to program crash/power failure, etc. Does
anyone know of a way of doing this?
You can avoid transaction begin/commit statements, so that
On 9 Aug 2010, at 5:05pm, Josh wrote:
I'm new to the list and had a question. I know the default behavior for
savepoints (or any transactions) is that if they have not been committed, if
the program crashes, they are lost. Is there any way to have them committed
by
default? Basically I
Thanks for the answers, but I guess I should have made my question more
clear. I knew that you can commit every sql statement individually, then
the question would be, how can I roll them back?
In other words I'd like something like savepoint and rollback to
savepoint, while not loosing the
[New text /below/ any text you want to quote, please.]
On 9 Aug 2010, at 9:09pm, Josh wrote:
Thanks for the answers, but I guess I should have made my question more
clear. I knew that you can commit every sql statement individually, then
the question would be, how can I roll them back?
