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

Ouverte
  • Quelque chose ne va pas ?
#753 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
54/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python, sql
Domaine
api, database

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Python
Étoiles
203
Forks
124
Merge moyen
14 h 14 min
PR mergées (30 j)
70

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de duckdb/duckdb-python

Toutes les issues de duckdb/duckdb-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.