db.sql.Connection() catalog and schema args surprisingly do not apply to metadata calls like cursor.tables
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with db.sql.Connection() and the cursor metadata calls catalogs(), schemas(), and tables(); compare their current behavior with the catalog and schema parameter documentation. Decide and document the parameters' scope and duration, including whether they provide defaults for metadata calls, and make the resulting behavior consistent.
Written by the indexing model from the issue text.
Description
Observation // Concern
catalog and schema initial values can be set when creating Connection. These values are not applied in subsequent cursor metadata calls: catalogs(), schemas(), and tables(). These functions are unaware of that previous setting.
Current documentation states:
:param catalog: An optional initial catalog to use. Requires DBR version 9.0+
:param schema: An optional initial schema to use. Requires DBR version 9.0+
Where both the scope and duration of application is unstated. It currently only applies to executed statement when opening the session. Metadata calls are entirely ignorant of this setting, which surprised at least one user, who expected the catalog setting to carry through in those calls.
Ask
Define and document scope of these parameters. Consider whether they should be applied, possibly as default values, to metadata calls.
- 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
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·