Unknown completion 'EXPLAIN'
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
I did an "EXPLAIN ANALYZE SELECT ..." call in Version 0.0.28:
🔥 SkunkException
🔥
🔥 Problem: Just constructed an unknown completion 'EXPLAIN'. Note that your
🔥 program has not crashed. This message is here to annoy you.
🔥 Hint: Please open an issue, or open a PR adding a case in Completion.scala
🔥 and a parser in CommandComplete.scala
Side note: The result of that is always a 'text' column, which is listed in the documentation as "not supported", although it apparently is.
Contributor guide
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 reading Completion.scala and CommandComplete.scala, then trace how an EXPLAIN ANALYZE response is parsed. Add the missing completion and parser handling described in the issue, and verify that the resulting text column behavior matches the documented support status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, scala
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100