Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
AW: Synchronization Data Model Constraints

AW: Synchronization Data Model Constraints

2007-03-05       - By Auer, Wolfgang

 Back
Reply:     1     2  

Hello Miguel,

The Synchronization Manager does not keep the originally update sequence.
Because of this a foreign key relationship could be violated.
In the case of a data collision the Synchronization Manager will refuse the
update of one table but may update the foreign key table. This would also lead
to a foreign key relationship violation.

>Anyone has experience with IN/OUT synchronization in MAXDB and can tell me if
all works ok?

Yes the bidirectional replication of tables works!

Regards
  Wolfgang


Wolfgang Auer
MaxDB&liveCache
SAP AG

Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, L
?o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso
Plattner
Registergericht/Commercial Register Mannheim No HRB 350269

Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung
oder Weitergabe der E-Mail ausdr?cklich untersagt.
Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise
confidential information. If you have received this e-mail in error, you are
hereby notified that any review, copying, or distribution of it is strictly
prohibited. Please inform us immediately and destroy the original transmittal.
Thank you for your cooperation.

-- --Urspr?ngliche Nachricht-- --
Von: Linos [mailto:info@(protected)]
Gesendet: Montag, 5. M?rz 2007 17:58
An: maxdb@(protected)
Betreff: Synchronization Data Model Constraints

Hello all,
  i am planning a development where i would like to use MaxDB
master/master synchronization (well in maxdb documentation it is called
IN/OUT sync between master and clients), i understand all the
constraints the design data model has to be but 1, this:

They may not contain foreign key relationships


Why? anyone knows? i would like to establish foreign key relationships
between replicated tables. Anyone has experience with IN/OUT
synchronization in MAXDB and can tell me if all works ok? Thanks in
advance.

Miguel Angel.


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=wolfgang.auer@(protected)


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)