databrickslabs / databrickslabs/lsql
[FEATURE] Introduce `escape_sql_identifier` to safely escape SQL identifiers like table, view and column names
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
See the code in ucx: https://github.com/databrickslabs/ucx/blob/125ccfa19b3f3bb3569e576b2f38ed4d62d13330/src/databricks/labs/ucx/framework/utils.py#L7.
Also use it in lsql where appropriate
Add it to backends or utils. Decide on what makes sense most
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 with the referenced ucx framework/utils.py implementation, then inspect lsql's backend and utility code to find where SQL identifiers are constructed. Determine the appropriate placement and usages for the escaping helper, covering table, view, and column names. Done means the helper exists and is used in the relevant lsql paths without changing other SQL behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100