-
Notifications
You must be signed in to change notification settings - Fork 286
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
reactor:multiple update executor #481
Conversation
在seata-go-sample项目中跑通了,再提交,这样能避免很多问题 |
After running through the seata-go-sample project, submit it again, which can avoid many problems |
好嘞,我下次注意下哈哈 |
Alright, I'll pay attention next time haha |
辛苦大佬哈 |
hard work boss |
请问大佬大名? |
May I ask the big guy's name? |
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #481 +/- ##
==========================================
- Coverage 39.02% 38.57% -0.45%
==========================================
Files 145 147 +2
Lines 9638 9949 +311
==========================================
+ Hits 3761 3838 +77
- Misses 5565 5793 +228
- Partials 312 318 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I'm Weide hahaha |
我是唯德哈哈哈 |
I'm Weide hahaha |
} | ||
|
||
// ExecContext exec SQL, and generate before image and after image | ||
func (m *multiExecutor) ExecContext(ctx context.Context, f exec.CallbackWithNamedValue) (types.ExecResult, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ExecContext 里面,直接判断该使用 MultiUpdateExeCutor 还是使用 MultiDeleteExeCutor,然后直接使用 executor.ExecContext() 方法。下面的beforeImage和afterImage方法就可以用都删了。这里没有逻辑的话,以后应该会更好维护
* reactor:multiple update executor
What this PR does:
refactor pkg/datasource/sql/undo/builder to pkg/datasource/sql/exec/at
Which issue(s) this PR fixes:
Fixes #439
Special notes for your reviewer:
Does this PR introduce a user-facing change?: