** Reply to message from "junzeng" <junzeng@netease.com> on Fri, 21 Mar 2003
11:00:39 +0800
Hi,
If you set the dissalow premature option in the odbc driver it can reduce the
risk of this - but it still does happen and it's extremely dangerous :(.
I have hacked the odbc driver (for the 7.72.0.5 level) to work with visualage
smalltalk, and have removed the rollback on error with no obvious bad side
effects. (there probably are some though).
Regards,
Wayne
> In a transaction , if a sql command invite an error , all commands before this
> command will be rollbacked , and the transaction reset and restart.
> For example:
>
> BEGIN
> insert t1 values(1);
> delete from t2
> insert t1 values(2);
> commit
>
> if table t2 doesn't exist , "delete from t2" invites an error , and the insert will be rollbacked .
>
> How can I prevent the rollback even when an error occurs ? Thanks