Hi Helen,

>A hard commit - COMMIT - probably uses less CPU resource than a soft
>commit. Its effect on performance overall is much better because of its
>favourable effect on garbage collection and the fact that the transaction
>resources get released.
>
>The question I think you really want to ask is whether it's a bad thing to
>commit every time you post. And the correct answer to this is
>"maybe". :-) It really gets down to how your users are working. If you
>have 100 users all editing the same 1000 rows in one table at random all
>day long, you probably need to make your commits instantaneously, to avoid
>a high level of conflicts. "Performance" to these users means not having
>to wait for someone else to come back from a coffee break. If you have
>apps that don't do much else except data entry of stuff that nobody is
>waiting for, then post-commit-post-commit isn't justified - it would be
>more efficient for the user and the network to let her batch her task and
>commit after every 20 inserts, or whatever works for her.
>
>
>

Last question. You say that commit is much favorable because it uses
less cpu and etc. but how about the resources needed to connect or open
transaction or open table again? Could this be not take to long?

Does IBO automatically make a commit if the application is close?

Thank you :-)

James

>/hb
>
>
>
>
>Yahoo! Groups Links
>
>To visit your group on the web, go to:
> http://groups.yahoo.com/group/firebird-support/
>
>To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
>Your use of Yahoo! Groups is subject to:
> http://docs.yahoo.com/info/terms/
>
>
>
>
>
>