Subject | Re: [IBO] some IBX method |
---|---|
Author | Jason Wharton |
Post date | 2003-07-08T07:29:21Z |
SavePoint method of the transaction is what you are looking for. It won't
force other datasets to be posted.
The converse of this is the LosePoint method to do a rollback retaining
without forcing datasets to be all cancelled.
LosePoint method is very new so if you don't have the latest then you won't
have this. (What people have done up to this point is to simply make the API
call directly which is really just about as easy.)
Jason Wharton
force other datasets to be posted.
The converse of this is the LosePoint method to do a rollback retaining
without forcing datasets to be all cancelled.
LosePoint method is very new so if you don't have the latest then you won't
have this. (What people have done up to this point is to simply make the API
call directly which is really just about as easy.)
Jason Wharton
----- Original Message -----
From: "james_027" <james_027@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, July 08, 2003 12:25 AM
Subject: [IBO] some IBX method
> The time when Iam using IBX this method is very useful for me ...
>
> for example I have add or edit to table1, I could just put these
> following lines ...
>
> table1.post;
> table1.transaction.commitretainning;
>
> this could just commit the changes you've made with table1 not
> affecting other tables
>
> but in IBO what I did is like this
> table1.post;
> maintransaction.commitretainning;
>
> but this could commit everything. Is there something like what I show
> in IBO. Iam to lazy to create another transaction for this table hehe
> =).
>
> thanks in advance.