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

New Doc: SQL Reference/Version Control Features/Merge #632

Closed
timsehn opened this issue Jun 7, 2022 · 3 comments · Fixed by #661
Closed

New Doc: SQL Reference/Version Control Features/Merge #632

timsehn opened this issue Jun 7, 2022 · 3 comments · Fixed by #661
Assignees
Labels

Comments

@timsehn
Copy link
Sponsor Contributor

timsehn commented Jun 7, 2022

  1. How conflicts are calculated
    1. data
    2. schema
  2. The dolt_conflicts and dolt_conflicts_<tablename> tables
    • Schema conflicts are not resolvable via SQL
  3. Resolving conflicts in SQL
    • Note must resolve in a single transaction
  4. Persisting conflicts to resolve later (not default)
@timsehn
Copy link
Sponsor Contributor Author

timsehn commented Jun 7, 2022

Conflict detection logic is specced here:

https://docs.dolthub.com/concepts/dolt/conflicts

Could be improved

@druvv
Copy link
Contributor

druvv commented Jun 7, 2022

Will come back to this after June 15th. Going to move forward on the suggestion to create a doc about merge in general in the SQL context.

@timsehn timsehn changed the title New Doc: SQL Reference/Version Control Features/Conflicts New Doc: SQL Reference/Version Control Features/Merge Jun 7, 2022
@timsehn
Copy link
Sponsor Contributor Author

timsehn commented Jun 7, 2022

New idea is to take all the content after:

https://docs.dolthub.com/sql-reference/version-control/branches#merging-branches

And rewrite it talking about AUTOCOMMIT off for merge. This has most of the content we want but can be combined with the ideas above to make a great doc we're proud of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants