Article View: borland.public.interbase.replication
Article #658Conflict handling
From: Ulrik Kristensen
Date: Fri, 02 Nov 2001 22:50
Date: Fri, 02 Nov 2001 22:50
86 lines
2416 bytes
2416 bytes
Typical scenario: 2 replication schemes : 1: From database A to B. 2: From database B to A. Scenario 1 (Using priority for conflict handling) Database 1: priority high Database 2: priority low. User update a row in database A at 9.11 User update a row in database B at 9.12 Replication at 9.13. Result record from database A is replicated to database B. Result is OK Scenario 2 (Using priority for conflict handling) Database 1: priority low. Database 2: priority high. User update a row in database A at 9.11 User update a row in database B at 9.12 Replication at 9.13. Result record from database A is replicated to database B. Result is BAD. Scenario 3 (Using timestamp for conflict handling) User update a row in database A at 9.11 User update a row in database B at 9.12 Replication at 9.13. Result record from database A is replicated to database B. Result is BAD. Scenario 4 (Using timestamp for conflict handling) User update a row in database A at 9.11 User update a row in database B at 9.10 Replication at 9.13. Result record from database A is replicated to database B. Result is OK. In all cases it was the order of the schemes 1, 2 and NOT PRIORITY or TIMESTAMP which was the determining factor. When changing to the schemes to 1: From database B to A. 2: From database A to B. Database B will always win over database A, no mater what the priority is or the values of the timestamp. This is a very serious BUG, which for me makes the product almost useless.
Technical Details
Message-ID:
<3be3234c$1_2@dnews>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!dnewsShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f89d7,49fe04b3ea01303c,start X-Google-Attributes: gidf89d7,public X-Google-ArrivalTime: 2001-11-02 15:10:44 PST From: "Ulrik Kristensen" <Admin@uk.dk> Newsgroups: borland.public.interbase.replication Subject: Conflict handling Date: Fri, 2 Nov 2001 23:50:51 +0100 Lines: 89 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 NNTP-Posting-Host: 213.237.15.230 Message-ID: <3be3234c$1_2@dnews> X-Trace: dnews 1004741452 213.237.15.230 (2 Nov 2001 14:50:52 -0800) Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!dnews