Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict management - take both client and server changes? #757

Closed
spj-uk opened this issue Jul 13, 2022 · 5 comments
Closed

Conflict management - take both client and server changes? #757

spj-uk opened this issue Jul 13, 2022 · 5 comments

Comments

@spj-uk
Copy link

spj-uk commented Jul 13, 2022

Is it possible when resolving conflicts to keep both items e.g.

Server: ID 2 Name "Bob"
Client: ID 2 Name "Jo"

Presumably ID would need to be changed / incremented and then inserted somehow.

@spj-uk spj-uk changed the title Conflict management - take both? Conflict management - take both client and server changes? Jul 13, 2022
@Mimetis
Copy link
Owner

Mimetis commented Jul 17, 2022

hello @spj-uk
I'm sorry, you can use the Merge option when dealing with conflicts, but to be in sync, both rows should have the same value

@spj-uk
Copy link
Author

spj-uk commented Jul 18, 2022

Thanks for replying. To confirm I want both rows in the synchronised database rather than to merge the records. i.e. Client ID 2 would have to become a new record with ID as it's a primary key. Is this possible?

@Mimetis
Copy link
Owner

Mimetis commented Jul 18, 2022

DMS will not be able to do that.

@VagueGit
Copy link
Contributor

The client must ensure unique ids. That's why DMS recommends using guids. It is possible to use sequential integer identifiers, but you will need an algorithm to generate identifiers that ensures uniqueness across devices even when disconnected.

@Mimetis
Copy link
Owner

Mimetis commented Jul 18, 2022

Take a look here : #590

@Mimetis Mimetis closed this as completed Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants