point for this type of
2 way replication setup.
John
-Original Message-
From: Gowtham Jayaram [mailto:[EMAIL PROTECTED]
Sent: Monday, March 01, 2004 1:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Replication / Synchronizing DB across different machines
>> But what happens i
>> But what happens if there is a break of
>> communication and the same record on both machines
>> is modified? For example, if the sync link is ?
>> down, and I update record #1 on A, while at the
>> same time, another user is modifying record #1 on
>> server B. When the link comes back onlin
Really? I didn't know that a single machine could act as both a slave and a
master for the same DB. H This opens a whole new world of
possibilities. Okay - I can understand the issue for autoincrement columns
becoming a problem. UIDs per server would need to be used in that case.
But
Yes,
Lets call the two serves A, and B. You set A as the master for B, and you set B as
the master for A. In this way you can insert/delete/update on either side and both
sides will be kept in sync. If you plan to actively use both at the same time you do
need to be weary of some syncroniza
