Article View: borland.public.interbase.replication
Article #10Re: Changing primary key and replicate this value
From: Jonathan Neve
Date: Mon, 23 Feb 2004 18:41
Date: Mon, 23 Feb 2004 18:41
18 lines
1970 bytes
1970 bytes
Paul Beach a οΏ½crit : > Er no. Only committed changes get replicated. > So this would really be insert PK=34 commit - Write replication insert to > replication log. > Then the insert takes place on the target with PK=34 data=blah > > Now if you update the primary key, and make it 35, commit, an update would > fail on the > target because replication expects to find the same primary key in the target > database > as the source i.e. update 35 which doesn't exist. Changing primary keys in > distributed databases (which includes replicated ones) is not the brightest > move. Yes. What I meant was : Insert -> Commit -> Update -> Commit -> Replicate. This, if I understand correctly, would indeed fail, right? Jonathan Neve.
Technical Details
Message-ID:
<403a4988@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<4034dce9$1@newsgroups.borland.com> <4034e8dc$1@newsgroups.borland.com> <4035deb9$1@newsgroups.borland.com> <mcic30d6avuml13ilsuokrerfncilfpjtu@4ax.com> <403653d3@newsgroups.borland.com> <4039b863$1@newsgroups.borland.com> <403a355b$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: f89d7,2f886c55ebe3c509 X-Google-Attributes: gidf89d7,public X-Google-ArrivalTime: 2004-02-23 11:11:07 PST Date: Mon, 23 Feb 2004 19:41:47 +0100 From: Jonathan Neve <jonathan@!nospam!microtec.fr> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.3.1) Gecko/20030425 X-Accept-Language: fr, en MIME-Version: 1.0 Newsgroups: borland.public.interbase.replication Subject: Re: Changing primary key and replicate this value References: <4034dce9$1@newsgroups.borland.com> <4034e8dc$1@newsgroups.borland.com> <4035deb9$1@newsgroups.borland.com> <mcic30d6avuml13ilsuokrerfncilfpjtu@4ax.com> <403653d3@newsgroups.borland.com> <4039b863$1@newsgroups.borland.com> <403a355b$1@newsgroups.borland.com> In-Reply-To: <403a355b$1@newsgroups.borland.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit NNTP-Posting-Host: 213.11.22.149 Message-ID: <403a4988@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1077561736 213.11.22.149 (23 Feb 2004 10:42:16 -0800) Lines: 19 Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail