Subject | RE: [ib-support] Child Tables Problem Revisited |
---|---|
Author | Doug Chamberlin |
Post date | 2001-10-31T15:42:45Z |
At 10/31/2001 10:25 AM (Wednesday), Bill Morrison wrote:
logic. For example,
1) Start Trans
2) Check for needing to delete existing record and delete it
3) Write new record
4) Commit
If you did it this way you would be sure the other process would see every
written record immediately after it was committed.
I'm curious as to why you commit every 15 writes or 15 seconds. Have you
tried something like I've suggested above and actually observed a
performance problem with it? That's the only reason I can think of not
committing every write.
>I am using the tiCommitted for the isolation level, and explicity commitingSounds to me that you should be committing every time you do the write
>after every 15 writes, or 15 seconds (the system averages 6 written records
>/ second). Commit-Retaining is not used. In addition, I have verified that
>the OAT is advancing normally. I cannot imagine how I could be any more
>specific with my transactions.
logic. For example,
1) Start Trans
2) Check for needing to delete existing record and delete it
3) Write new record
4) Commit
If you did it this way you would be sure the other process would see every
written record immediately after it was committed.
I'm curious as to why you commit every 15 writes or 15 seconds. Have you
tried something like I've suggested above and actually observed a
performance problem with it? That's the only reason I can think of not
committing every write.