Re: AW: Synchronization Data Model Constraints
Linos <[email protected]>
| Newsgroups | gmane.comp.db.maxdb |
|---|---|
| Message-ID | <[email protected]> |
Thanks Wolfgang, i will have to pass the cascade functions and integrity checks (about foreign keys) from the database to the application layer, well it is not the end of the world :). El lun, 05-03-2007 a las 18:30 +0100, Auer, Wolfgang escribió: > 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:[email protected]] > Gesendet: Montag, 5. März 2007 17:58 > An: [email 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/[email protected]