You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now there is a procedure called DOLT_CONFLICTS_RESOLVE() that can resolve all conflicts within a table using ours or theirs, however it would be helpful to have a similar procedure that could resolve a conflict to ours or theirs using the unique ID for a given conflict.
The text was updated successfully, but these errors were encountered:
Thanks for the great feature request! 🙏 It seems like we could support an optional fourth parameter to DOLT_CONFLICTS_RESOLVE() that would let you pass in the conflict hash so you could scope down the resolution to a single conflict.
Implementation-wise... this is a little more involved than the current implementation, since at a table granularity, it's very easy to swap a whole table between roots, but working on an individual row granularity should still be pretty straightforward.
Right now there is a procedure called
DOLT_CONFLICTS_RESOLVE()
that can resolve all conflicts within a table using ours or theirs, however it would be helpful to have a similar procedure that could resolve a conflict to ours or theirs using the unique ID for a given conflict.The text was updated successfully, but these errors were encountered: