Audit `LOCATE` function for edge cases
Open
Nobody has claimed this yet.
correctness
- Dominant language
- Go
- Stars
- 24.5k
- Forks
- 873
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 120
Description
This is a follow-up to #11393 and addresses @jycor's comment on dolthub/go-mysql-server#3671. We want to make sure LOCATE works properly for NULL and other edge case inputs (like other types that convert to numbers).
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 at the LOCATE implementation and review the context in #11393 and dolthub/go-mysql-server#3671, then exercise NULL and other type-conversion edge cases. Done means LOCATE behavior is verified or corrected for those inputs, with tests covering the identified cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100