Closed
Conversation
Closed
Member
|
后面的 Scan 和前面的 Create 没有从属关系的，是两次 SQL 生成 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What did this pull request do?
关于on duplicate key update 后scan 的bug 测试样例
User Case Description
如果on duplicate key update 执行的是 price = price+ 0 这样无改动的语句时，后面再执行Scan。会把sql中所有记录扫出来，Debug()一下，发现执行的是SELECT * FROMproductsWHEREproducts.deleted_at IS NULL