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

[Question] DML语句中虽然有where条件,但无法通过数量校验 #1096

Open
1 task done
lurise opened this issue Sep 13, 2024 · 3 comments
Open
1 task done

Comments

@lurise
Copy link

lurise commented Sep 13, 2024

描述问题
已通过设置限制最大变更数量为1000,编写的DML使用where条件限制了变更范围,但点击检验时,显示超过数量限制;通过数据库连接软件查询限制条件,实际并未超过上述限制。

期望的结果
清晰而简洁地描述你希望得到的结果

部署方式

  • Docker

环境 (请填写环境信息):

  • 操作系统: windows
  • 浏览器 Chrome
  • 版本号 ver.3.1.7
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Title: [Question] Although there is a where condition in the DML statement, it cannot pass the quantity check.

Describe the problem
The maximum number of changes has been set to 1,000. The DML written uses the where condition to limit the scope of changes. However, when you click the check button, it shows that the number limit has been exceeded. The restriction conditions are queried through the database connection software, and the above limit is not actually exceeded.

Desired results
Clearly and concisely describe the results you hope to achieve

Deployment method

  • Docker

Environment (please fill in environmental information):

  • Operating system: windows
  • Browser Chrome
  • Version number ver.3.1.7

@cookieY
Copy link
Owner

cookieY commented Sep 25, 2024

影响行数基于Explain分析SQL语句的影响行数。由于Explain生成的影响行数受主键,索引等其他因素的影响,并不能100%保证其准确性。其更多的是反应了该语句导致的全表扫描行数,所以对于误差较大的语句具有一定的优化参考意义。

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


The number of affected rows is based on the Explain analysis of the number of affected rows of the SQL statement. Since the number of rows generated by Explain is affected by primary keys, indexes and other factors, its accuracy cannot be guaranteed 100%. It more reflects the number of rows scanned in the entire table caused by the statement, so it has certain optimization reference significance for statements with large errors.

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

No branches or pull requests

3 participants