Meituan-Dianping / Meituan-Dianping/SQLAdvisor
只能对简单的单表或2个表 join 做分析,对于复杂SQL冗余或复杂的基本上分析不了
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5.6k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
[root@localhost ~]# sqladvisor -u mpup -p mpup -P 3306 -h 127.0.0.1 -d mpup -q "select log_id,user_name,log_type,log_createtime,log_level,log_formatter from (select log_id,user_name,log_type,log_createtime,log_level,log_formatter from (select log_id,user_name,log_type,log_createtime,log_level,log_formatter from LOG order by log_createtime desc,log_id asc ) orderedLog ) logs limit 0, 10;" -v 1
2017-11-09 17:29:17 5726 [Note] 第1步: 对SQL解析优化之后得到的SQL:select log_id AS log_id,user_name AS user_name,log_type AS log_type,log_createtime AS log_createtime,log_level AS log_level,log_formatter AS log_formatter from (select log_id AS log_id,user_name AS user_name,log_type AS log_type,log_createtime AS log_createtime,log_level AS log_level,log_formatter AS log_formatter from (select log_id AS log_id,user_name AS user_name,log_type AS log_type,log_createtime AS log_createtime,log_level AS log_level,log_formatter AS log_formatter from mpup.LOG order by log_createtime desc,log_id) orderedLog) logs limit 0,10
2017-11-09 17:29:17 5726 [Note] 第2步:表* 是临时表,不进行处理
2017-11-09 17:29:17 5726 [Note] 第3步:表* 是临时表,不进行处理
2017-11-09 17:29:17 5726 [Note] 第4步: SQLAdvisor结束!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied sqladvisor command and compare its output with the nested-query structure in the issue. Trace the SQL analysis path where the derived tables are reported as temporary tables; done should include meaningful analysis or index recommendations for this complex query rather than stopping at those messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100