alexander-beedie opened a new issue, #1000:
URL: https://github.com/apache/arrow-adbc/issues/1000
It seems something has changed between the 0.5.x and 0.6.x releases, and you
can no longer reference the standard `main` db schema in SQLite queries.
Note that `main` should _always_ be valid, as it refers to the primary db
being connected to (other names can be brought in via `ATTACH DATABASE`).
The following minimal test-case demonstrates the issue:
```python
from adbc_driver_sqlite.dbapi import connect
import pyarrow as pa
data = pa.Table.from_pydict( {"key":["aa","bb","cc"],"value":[10,20,30]} )
with connect() as conn, conn.cursor() as crsr:
crsr.adbc_ingest( "main.test_data", data, "create" )
conn.commit()
crsr.execute( "SELECT * FROM main.test_data" )
print( crsr.fetch_arrow_table() )
# pyarrow.Table
# key: string
# value: int64
# ----
# key: [["aa","bb","cc"]]
# value: [[10,20,30]]
```
On previous versions (0.5.x) this works correctly, as expected.
In the latest release (0.6.x) it raises the following exception instead:
```
adbc_driver_manager._lib.InternalError: ADBC_STATUS_INTERNAL (9):
[SQLite] Failed to prepare statement: no such table: main.test_data
(executed 'INSERT INTO main.test_data VALUES (?, ?)')
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
