Hi Helen,

with all due respect, I put a little test together using StartTransaction /
CommitRetaining / then reissued the Query to refresh and ran this
simulatenous on two computers. Ttable changes made on one computer, I can
see after a refresh on the both computers.

Best Regards
Hans

----------------------------------------------------------------------

----- Original Message -----
From: "Helen Borrie" <helebor@...>
To: <firebird-support@yahoogroups.com>
Sent: Monday, September 01, 2003 12:45 AM
Subject: Re :[firebird-support] Update & Syncronization prpblem


| At 01:36 PM 1/09/2003 +0700, you wrote:
|
|
|
| >I will Study about the literature, just one question, what do you mean by
| >Hard Commit ?
|
| Calling COMMIT, not COMMITRETAINING (a.k.a. "soft commit").
|
| COMMIT WITH RETAIN ("CommitRetaining") was a hack introduced by Borland to
| support the BDE components, to support a design which disguises the
| transaction mechanism and makes inexperienced programmers think they are
| working with Paradox. If you don't understand what you are doing, blindly
| writing applications that use only CommitRetaining has some other serious
| side-effects which cause your server to slow down, freeze and, eventually,
| to crash.
|
| CommitRetaining commits (ends) the transaction and then starts a new
| transaction with the same transaction context (cursor sets) as the
original
| one. If transaction isolation is SNAPSHOT ("concurrency") this means that
| the application continues to see the database state exactly as it was when
| the original transaction started - even after a refresh (requery) it can
| see changes that were made inside its own context but it can't see changes
| done by others. A SNAPSHOT transactions will get a fresh view of database
| state after a "hard" COMMIT.
|
| heLen
|
|
|
|
| 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/
|
|
|