[BUG] `duckdb` visualization broken in `1.4.0` and onwards

[RaczeQ]

Context

What results were you expecting?

when calling viz function with duckdb relation it throws AssertionError: One column must have GeoArrow extension metadata error.

Resulting behaviour, error message or logs

Code skips duckdb detection and goes straight to __arrow_c_stream__ check.

It seems like this check stopped working:

if (
        data.__class__.__module__.startswith("duckdb")
        and data.__class__.__name__ == "DuckDBPyRelation"
    ):
        return _viz_duckdb_relation(data, **kwargs)  # type: ignore

    if (
        data.__class__.__module__.startswith("duckdb")
        and data.__class__.__name__ == "DuckDBPyConnection"
    ):
        raise TypeError(DUCKDB_PY_CONN_ERROR)

Because now DuckDB module looks like this: <class '_duckdb.DuckDBPyRelation'>

Environment

• OS: WSL Ubuntu
• Browser: N/A
• Lonboard Version: 0.12.1

Steps to reproduce the bug

import duckdb
from lonboard import viz

relation = duckdb.read_parquet(...)

viz(relation)

[kylebarron]

Thanks for the report.

This should work if you call:

duckdb.sql("CALL register_geoarrow_extensions()")

which should apparently be registered automatically in duckdb 1.5: duckdb/duckdb-spatial#589

And from the report I figure calling from_duckdb on a layer directly works still.

But for now we can reorder the checks in viz to check for duckdb ahead of a generic PyCapsule interface check