Compiled sql for an input list parameter results in incorrect syntax in 4.0.4
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Reproduce the 4.0.4 case with a list parameter such as [1, 2, 3] and inspect the path that compiles the SQL for input parameters. Confirm that an IN clause no longer produces ARRAY(1, 2, 3), and that the completed output uses the valid form IN (1, 2, 3).
Written by the indexing model from the issue text.
Description
In 4.0.4 it seems like the partial implementation of supporting complex types like arrays etc is resulting in incorrect syntax
For example (where the list parameter is [1, 2, 3]):
… WHERE something IN %s
Is resulting in:
… WHERE something IN ARRAY(1, 2, 3)
Which is invalid syntax as of the current runtime. It should be
… WHERE something IN (1, 2, 3)
- Dominant language
- Python
- Stars
- 233
- Forks
- 152
- Avg merge
- 21h 5m
- Merged PRs (30d)
- 10
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.
More from databricks/databricks-sql-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
All issues in databricks/databricks-sql-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·