eeroel/ipykernel-duckdb

IPykernel wrapper with autocompletion and magics for DuckDB

ipykernel-duckdb's Issues

Check if database is open before scanning user namespace

Autocomplete doesn't work when column name is quoted

• Expected behavior: when typing E we should get a completion "Eye color"
• What happens: no completion

Make demo notebook self-contained

I.e. use in-memory database and create data in the notebook

Autocomplete should suggest tables or columns based on context

E.g. select _ <- columns, from _ or join _ <- tables; group by _ <- valid grouping columns.
This likely requires actual SQL parsing though.

Look into integrating with ipython-sql

It would be nice if the autocomplete would be usable with any DB, not just duckdb, so this might be possible using ipython-sql (e.g. just load the extension and use sqlalchemy to get table+column names)

Handle aliases in deduplication

• Deduplication key should consider table name and its alias the same
• For alias SimpleNamespaces we don't want to list the unprefixed columns (as they're always included with the actual table)

On the other hand, we can just deduplicate on the output text separately

Completions don't update properly

1. create database
2. make queries
3. create new database with different table
   => completions are still from database A

Possible causes:

• We're in fact picking up a different database object from ipython history...

Write tests

• Test autocompletion logic
• Use tox to test build in different envs?

Autocomplete matches substrings of table names

E.g. table "foo" will be matched to "foo_bar" so
select _ from foo_bar will get suggestions to columns of "foo" as well

Check why autocomplete is wrong in classic notebook

Autocomplete doesn't suggest column names after arithmetic operator

E.g. select foo-_ from bar gets no suggestion