Subject | Re: [IBO] Best Practise on committing |
---|---|
Author | James |
Post date | 2004-03-23T03:39:34Z |
Hi
jtsiy wrote:
lot of options here. It really depends if the data needs to be post and
commit at once. In my experience on a scenario wherein data needed to be
post and commit right way, I use ib_transaction.refresh(true);
For closing and opening dataset. I simple do ib_query.close and
ib_query.open. I have read some use ib_query.unprepare and
ib_query.open. Don't know if refresh will do. Perhaps some gurus here
will answer that for you.
Cheers,
james
jtsiy wrote:
> Dear IBO usersYes. Once Helen has told me that commitretaining is not good. You got a
>
> What is the best my of doing commit that still leaves the dataset open?
>
> I read that commitretaining/rollbackretaining isn't a good practice
> cause it consume much more memory + prodcue some OAT problems.
>
> How about if I need to close and open a dataset due to some changes in
> the SQL statement. Will refresh do the trick?
>
lot of options here. It really depends if the data needs to be post and
commit at once. In my experience on a scenario wherein data needed to be
post and commit right way, I use ib_transaction.refresh(true);
For closing and opening dataset. I simple do ib_query.close and
ib_query.open. I have read some use ib_query.unprepare and
ib_query.open. Don't know if refresh will do. Perhaps some gurus here
will answer that for you.
Cheers,
james