Subject | Re: DMLCache and DMLCacheReceivedItem not fired |
---|---|
Author | Marco Menardi <mmenaz@lycosmail.com> |
Post date | 2003-02-01T21:42:16Z |
Are the two dataset linked with two different transaction components?
My "test app" that I've build to isolate the problem, does not work on
post, only with commit, and an explicit one (well, even a rollback
fires the DMLCache... strange...).
If you have the two datasets inside the same transaction, a post is
enought.
Marco Menardi
My "test app" that I've build to isolate the problem, does not work on
post, only with commit, and an explicit one (well, even a rollback
fires the DMLCache... strange...).
If you have the two datasets inside the same transaction, a post is
enought.
Marco Menardi
--- In IBObjects@yahoogroups.com, "Thomas Steinmaurer" <ts@i...> wrote:
> Hi Marco,
>
> > Shame on me :((
> > My "base table editing form" had a transaction component that, I don't
> > know why, had a tiConcurrency isolation level :(
> > I've changed it to tiCommitted (the level I always use for this kind
> > of editing, so I did not check it until now) as suggested by Thomas
> > Steinmaurer in his first post and everything works!
> > But I think that some documentation has to be improved. My setup
> > should have been correct because I need things work that way, but as
> > far as I remember, is not obvious from the tech-sheet nor the help
> > file that:
> > a) you have to explicitly commit changes, autocommit is not enought if
> > your datasets are chained with different transactions
>
> my small test application based on your initial post works
> also with TIB_Transaction.AutoCommit = True, so I guess an
> explicit commit isn't needed as long you don't start an
> explicit transaction with TIB_Transaction.StartTransaction.
>
>
> Regards,
> Thomas.