Meituan-Dianping / Meituan-Dianping/SQLAdvisor
Segmentation fault
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5.6k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
select * from rocket_release where end_time>start_time order by id desc
日志：
2020-06-03 15:38:00 7482 [Note] 第1步: 对SQL解析优化之后得到的SQL:select * AS * from nasa.rocket_release where (end_time > start_time) order by id desc
2020-06-03 15:38:00 7482 [Note] 第2步：开始解析join on条件:end_time=start_time
Segmentation fault
没看实现代码，但是估计是识别解析的逻辑有问题，不知道这里为什么会有join on条件
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 crash with the reported SELECT statement and compare the parser log stages, especially the WHERE comparison that is reported as a join condition. Trace SQLAdvisor's SQL parsing and join-condition handling to determine why this input reaches that path. Done means the query parses without a segmentation fault and no longer produces an incorrect join-condition interpretation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100