Subject | Re: [IBO] DML updating using tib_cursor |
---|---|
Author | Helen Borrie |
Post date | 2002-09-25T22:37:43Z |
At 02:54 PM 25-09-02 -0500, you wrote:
tiCommitted, then it won't see the outcome of the DML until next time its
transaction is committed via a hard commit, even if you refresh it in
response to a DMLCaching signal.
Don't use CommitRetaining for your on-the-fly SQL statement's transaction,
since the purpose of CommitRetaining is to retain the same transaction
context. This will affect the rowset which the update statement's
transaction can see as "eligible".
Helen
>How do I update a master-detail setup using anWhat transaction isolation are your datasets running in? If it's not
>_external_ tib_cursor to make record updates
>to the detail:
> On a master record and a detail record linked by
>mastersource/masterlink system I need to make a
>update of a date in all of the detail records linked
>to the master. But I need to show this updating in
>a grid. I use a tib_cursor with a on-the-fly sql
>statement that changes the fields and then commits
>(commitretaining). This does not reflect in the grid
>though, even though DML flags are all set. Refresh
>of the master does not seem to reflect these changes..
>How? (TIA)
tiCommitted, then it won't see the outcome of the DML until next time its
transaction is committed via a hard commit, even if you refresh it in
response to a DMLCaching signal.
Don't use CommitRetaining for your on-the-fly SQL statement's transaction,
since the purpose of CommitRetaining is to retain the same transaction
context. This will affect the rowset which the update statement's
transaction can see as "eligible".
Helen