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
I mean Execute an SQL statement and immediately synchronize commit it.
And only commit the modifications caused by this single SQL statement instead of committing the entire table.
for instance:
maybe like this
mysql>call dolt_execute_and_commit('-m','info','-sql','update *')
The text was updated successfully, but these errors were encountered:
Thanks for the feature suggestion, @GodGavin. I understand the appeal for this to be all wrapped up in a single, easy-to-execute statement and I see how that could be handy for customers.
For others reading this issue, the workaround would be to create a branch, execute the update/insert, create a dolt commit on the branch, and merge the branch back to the starting branch (or alternatively, cherry-pick the new commit on the branch to avoid creating a merge commit on the starting branch in case its history has moved forward). The effect and isolation of the changes should be the same, but obviously having this in a single command to execute would be a simpler experience for customers.
I mean Execute an SQL statement and immediately synchronize commit it.
And only commit the modifications caused by this single SQL statement instead of committing the entire table.
for instance:
maybe like this
mysql>call dolt_execute_and_commit('-m','info','-sql','update *')
The text was updated successfully, but these errors were encountered: