DuckDBPyRelation.create_view cannot create a view in another schema or database

未关闭
  • 哪里不对？
#753 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
54/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python, sql
领域
api, database

调研方向

Start at the public DuckDBPyRelation.create_view and to_view implementations and trace how they pass the view name to the connection; the issue identifies private _create_view and _render as a working reference. Reproduce with the supplied script, including a qualified schema name and attached database, then check that the public API can create views at those paths while preserving relation parameters and referenced Python objects.

由索引模型根据 Issue 内容生成。

描述

We'd like to use rel.create_view("schema_name.view_name") to create the view view_name under the schema schema_name, but currently have to resort to calling the private methods and functions con._create_view and relation._render.

[!NOTE]
The following content was generated by AI.

What happens?

DuckDBPyRelation.create_view(view_name) (and to_view) takes one identifier. A qualified name is not split: rel.create_view("s.v") creates a view literally named "s.v" in memory.main, not a view v in schema s. There is no public way to create a view of a relation in another schema, another attached database, or a nested schema (DuckDB 2.0).

The workarounds lose what create_view gives. CREATE VIEW s.v AS {rel.sql_query()} reads the Python objects the relation scans by an internal name, so it fails once the relation is gone ("This query reads a pandas DataFrame or NumPy array that was released"), and it breaks on a relation with parameters ("Values were not provided for the following parameters"). The private con._create_view(path, sql) with _render(rel, literals=True, wrap_text=True) does exactly the right thing and already accepts a tuple path, nested schemas included.

We use that private call in datarecord to register a record's relations as views (<db>.<name>.dims.<dim>) that SQL clients read over a DuckDB server, and have to cap duckdb at the release we tested because of it.

Could create_view / to_view accept a qualified name, for example a tuple ("s", "nested", "v") like _create_view, or schema= / catalog= arguments?

To Reproduce
import duckdb
from duckdb._relation import _render

con = duckdb.connect()
con.sql("CREATE SCHEMA s; CREATE SCHEMA s.nested; ATTACH ':memory:' AS other")
rel = con.sql("SELECT 42 AS x")

rel.create_view("s.v")
rel.create_view("other.main.v")
print(con.sql(
    "SELECT database_name, schema_name, view_name FROM duckdb_views() "
    "WHERE NOT internal ORDER BY ALL"
).fetchall())
# [('memory', 'main', 'other.main.v'), ('memory', 'main', 's.v')]
# expected: ('memory', 's', 'v') and ('other', 'main', 'v')

con._create_view(("s", "nested", "w"), _render(rel, literals=True, wrap_text=True)[0])
print(con.sql("FROM s.nested.w").fetchall())  # [(42,)]: the private call does it
OS:

Linux x86_64

DuckDB Package Version:

2.0.0

Python Version:

3.14.6

Full Name:

Jonas Hörsch

Affiliation:

Open Energy Transition

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release (2.0.0)

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Did you include all code required to reproduce the issue?
  • Yes, I have
Did you include all relevant configuration to reproduce the issue?
  • Yes, I have
主要语言
Python
星标
203
派生
124
平均合并
14 小时 14 分钟
30 天内合并 PR
70

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

duckdb/duckdb-python 的其他 Issue

查看 duckdb/duckdb-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。