🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.interbase.replication
Article #138

Re: Bi Way replication does not complete

#138
From: AG
Date: Sat, 24 Jan 2004 06:15
12 lines
1559 bytes
My mistake....the replication is set to run continuously. That begs
the question...if there is no data to replicate what data is being
sent between the two databases. Is is possible to set the replication
that if no data is to be replicated then the replication stops until
more data is inserted into the database? My main question though is
what is causing such massive downloads when both databases are up to
date. (The repl_log table shows entries but these are just left overs
from how the replication was set up - certain tables were removed from
the replication setup and this is the left over data so in real terms
the repl_log table is being cleared)
Thanks
Anthony
Technical Details
Message-ID: <6c4c673a.0401232215.4ef12498@posting.google.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail
References: <6c4c673a.0401230439.3548be6e@posting.google.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f89d7,d9cc047b35bb4cb5
X-Google-Attributes: gidf89d7,public
X-Google-ArrivalTime: 2004-01-23 22:15:58 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail
From: akgough@ozemail.com.au (AG)
Newsgroups: borland.public.interbase.replication
Subject: Re: Bi Way replication does not complete
Date: 23 Jan 2004 22:15:58 -0800
Organization: http://groups.google.com
Lines: 12
Message-ID: <6c4c673a.0401232215.4ef12498@posting.google.com>
References: <6c4c673a.0401230439.3548be6e@posting.google.com>
NNTP-Posting-Host: 203.166.96.235
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1074924958 9449 127.0.0.1 (24 Jan 2004 06:15:58 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 24 Jan 2004 06:15:58 +0000 (UTC)