Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Field modification replication problem

2 posts in Replication Last posting was on 2006-03-09 11:29:39.0Z
Benoit claeys Posted on 2006-03-09 09:34:41.0Z
Reply-To: "Benoit claeys" <benoit.claeys@brainstorming.be>
From: "Benoit claeys" <benoit.claeys@brainstorming.be>
Newsgroups: advantage.Replication
Subject: Field modification replication problem
Date: Thu, 9 Mar 2006 10:34:41 +0100
Lines: 32
Organization: Silicon Brain
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 213.177.74.243
Message-ID: <440ff48e@solutions.advantagedatabase.com>
X-Trace: 9 Mar 2006 02:25:34 -0700, 213.177.74.243
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.177.74.243
Xref: solutions.advantagedatabase.com Advantage.Replication:97
Article PK: 1133954

I change two different fields (not primary record value) on a same record in
two cross replicated dictionnaries at almost the same time.
the result is an complete record exchange !!
example :
Starting point :
DicA record 1 : field1 value 'AA' field2 value 'BB'
DicB record 1 : field1 value 'AA' field2 value 'BB'

Simulaneous modification on both dic:
DicA record 1 : field1 value 'AM' field2 value 'BB'
DicB record 1 : field1 value 'AA' field2 value 'BM'

After replication:
DicA record 1 : field1 value 'AA' field2 value 'BM'
DicB record 1 : field1 value 'AM' field2 value 'BB'

This result is not as espected : we have a record exchange !!!
Usual replication on a push model must only push modified fields.
Engine have to compare [Oldvalue] and [NewValue] on each field to detect
and push modified field value only.

What I expect for result in a replication process is :
DicA record 1 : field1 value 'AM' field2 value 'BM'
DicB record 1 : field1 value 'AM' field2 value 'BM'

Do I something wrong ?

best regards
Benoit CLAEYS


Joachim Duerr (ADS Support) Posted on 2006-03-09 11:29:39.0Z
From: "Joachim Duerr (ADS Support)" <jojo.duerr@gmx.de>
Subject: Re: Field modification replication problem
Newsgroups: Advantage.Replication
References: <440ff48e@solutions.advantagedatabase.com>
Organization: iAnywhere
User-Agent: XanaNews/1.17.6.5
X-Face: ,QMv7[luB)BpWAQ~:"kw6n%0ieY63.:g2K3n~8ky0;||5Xle*Xq+=~<Fy:0CVC2nx@8~vZ
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 195.2.185.25
Message-ID: <441011a3@solutions.advantagedatabase.com>
Date: 9 Mar 2006 04:29:39 -0700
X-Trace: 9 Mar 2006 04:29:39 -0700, 195.2.185.25
Lines: 13
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!195.2.185.25
Xref: solutions.advantagedatabase.com Advantage.Replication:98
Article PK: 1133955


Benoit claeys wrote in <440ff48e@solutions.advantagedatabase.com>:

> Do I something wrong ?

no. You don't.
ADS pushes the whole record to the other site...and if you don't define
an ON CONFLICT Trigger, you'll get this result.

--
Joachim Duerr
Senior Product Support Analyst (Advantage Database Server)
iAnywhere Solutions / Extended Systems
advantage[AT]extendsys.de