Subject | Re: [IBO] Cached Updates and CommitUpdates |
---|---|
Author | Matt Nielsen |
Post date | 2004-12-27T15:05:14Z |
I've done a bunch of testing and I get Invalid pointer operations on
some delete operations if I do the CommitUpdates after the
Transaction commit. When I put it before the Transaction commit it
works fine as far as I can tell.
Why would this be?
Thanks,
Matt
some delete operations if I do the CommitUpdates after the
Transaction commit. When I put it before the Transaction commit it
works fine as far as I can tell.
Why would this be?
Thanks,
Matt
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> At 09:39 PM 16/12/2004 +0000, you wrote:
>
>
> >In what order should I use the CommitUpdates in regards to a
> >transaction? Before the Transaction Commit or After?
>
> After.
>
> ApplyUpdates is equivalent to Post in the "live" model, i.e. it
loops
> through the cache and posts the changed and inserted records and
the
> deletions; Commit commits the transaction; CommitUpdates doesn't
commit
> anything, but resets (empties) the cache buffer.
>
> Your other problem is probably due to being (justifiably!!)
confused by the
> name of the CommitUpdates method. Beats me why Borl didn't name it
> ClearCacheBuffer or something similar.
>
> Helen