Principles of Replication

Article View: borland.public.interbase.replication

Article #686

Back to borland.public.interbase.replication Previous Next

#686

From: Geoff Marshall
Date: Fri, 21 Sep 2001 15:59

18 lines
1466 bytes

I'm intrigued to know how the replicator works in one particular
respect.

Database A is changed by a user

Replication changes Database B

What stops the change to database B being replicated back to database
A?  

I assume that operator changes to database B are not blocked while the
replicator runs so it's a question of how does the replicator know which
changes to database B were done by itself (and must not be replicated
back to database A) and those updated by the user (which are required to
be replicated back to A).


Geoff Marshall

Technical Details

Message-ID: <3BAB63CF.405A24A5@gemsys.co.uk>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!cpk-news-hub1.bbnplanet.com!news.gtei.net!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f89d7,a226d581b652eec6,start
X-Google-Attributes: gidf89d7,public
X-Google-ArrivalTime: 2001-09-21 09:14:14 PST
Message-ID: <3BAB63CF.405A24A5@gemsys.co.uk>
Date: Fri, 21 Sep 2001 16:59:11 +0100
From: Geoff Marshall <Geoff@gemsys.co.uk>
X-Mailer: Mozilla 4.7 [en-gb] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: borland.public.interbase.replication
Subject: Principles of Replication
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 213.120.116.140
X-Trace: dnews 1001087401 213.120.116.140 (21 Sep 2001 08:50:01 -0700)
Lines: 18
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!cpk-news-hub1.bbnplanet.com!news.gtei.net!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews