[Rafael Viana]

'Rafael wrote:

Yes, I got it. Using in this way, will it work with INSERT/UPDATE/DELETE?

I already didn't receive an answer from sales team… Do you know how many days do I need to wait for an answer?

I was testing it with composite primary key. However, I can't use it.

Is there another way?

[Rafael Viana]

'peterlaursen' wrote:

You should understan 2 things:

1) A bidirectional/two-way sync is simple a one-ways sync in one direction (source –> target) followed by another onw-way sync in the other direction (source and target now reverted).

2) For either sync's rows with the same PK-value target will be updated (or 'overwritten) wiht the soruce row.

Consider you have data

source table:

Code:

PK other_column

1 a

target table:

Code:

PK other_column

1 b

Note that they have the same PK-value. The first sync will overwrite 'b' wiht 'a' on target. Nnext sync does nothing as tables are identical.

If you want to insert on two databases between sync the PK must be defined in such a way that the same PK-value will not be created on boths host. One way to achieve this is to add a column one ach table having different defaults on the two and include this column in the PK.

Did I get the point/problem?

Yes, I got it. Using in this way, will it work with INSERT/UPDATE/DELETE?

I already didn't receive an answer from sales team… Do you know how many days do I need to wait for an answer?

[Rafael Viana]

'peterlaursen' wrote:

Could I ask you to create a support ticket with our sales team? You do so by sending a mail to [email protected]

Ok. Thanks.

[Author]

Posts