Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

MySQL ADBC driver ignores the target schema when creating an ingest table

Offen
  • Stimmt etwas nicht?
#258 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
mysql, python
Bereich
database

Rechercherichtung

The workaround lives in xarray_sql/backends/adbc.py, in _default_database, which switches the connection's default database for MySQL and MariaDB. The root bug is in the upstream adbc-drivers/mysql driver, so the first step is to reproduce it with the snippet in the issue and file the upstream report. Done here means the upstream issue exists and test_mysql_mixed_dimensions_register_in_a_database passes with XARRAY_SQL_TEST_MYSQL_URI set; removing the workaround waits for a fixed driver release.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

The ADBC Driver Foundry's MySQL driver (0.6.1, the latest release at the time of writing) ignores the target schema when it creates the table for an ingest. Given db_schema_name, it creates the table in the connection's default database, then inserts into the target database, so the ingest fails.

#255 works around this in the ADBC adapter. This issue tracks the workaround until the driver is fixed.

Reproduction

MySQL 8.4.11, adbc-driver-manager 1.12.0, MySQL driver 0.6.1 (dbc install mysql):

import pyarrow as pa
from adbc_driver_manager import dbapi

con = dbapi.connect(driver="mysql", db_kwargs={"uri": "mysql://[email protected]:3306/xql"})
with con.cursor() as cur:
    cur.execute("CREATE DATABASE IF NOT EXISTS era5")
    cur.adbc_ingest("surface", pa.table({"x": [1.0]}), mode="create", db_schema_name="era5")

  • Expected: a table era5.surface holding one row.

  • Actual:

    ProgrammingError: NOT_FOUND: [MySQL] failed to prepare batch insert statement:
Error 1146 (42S02): Table 'era5.surface' doesn't exist.

    The table was created as xql.surface, in the connection's default database, according to information_schema.tables.

Workaround in xarray-sql

For MySQL and MariaDB, xarray_sql/backends/adbc.py doesn't pass db_schema_name at all. Instead, _default_database makes the target database the connection's default (USE era5) for the duration of the ingest, then restores the previous default. MySQL can't unset a default database, so a connection that had no default keeps the target afterwards.

This is how mixed-dimension Datasets register as era5.<group> on MySQL. test_mysql_mixed_dimensions_register_in_a_database covers it; the test runs when XARRAY_SQL_TEST_MYSQL_URI is set.

Next steps

  • Report upstream at adbc-drivers/mysql (no existing issue covered it at the time of writing).
  • Once a fixed driver is released, remove _default_database and pass db_schema_name through on MySQL, as on every other database.

🤖 Generated with Claude Code

Vorherrschende Sprache
Python
Sterne
142
Forks
19
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
9

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus xqlsystems/xarray-sql

Alle Issues in xqlsystems/xarray-sql

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.