mobilitydb_network × ducklink bridge (Phase 9.2, mobilitydb)

Auto-generated by sqlink-shim-codegen via --dynlink --target mobilitydb_network --provider-id mobilitydb_network-composed.

What this is

A wasm32-wasip2 cdylib that imports compose:dynlink/linker@0.1.0 and exports the canonical duckdb:extension@4.0.0 contract. At LOAD time the host's provider registry resolves the id mobilitydb_network-composed to the per-sub composed shim provider under datafission/extensions/mobilitydb/deps/mobilitydb-network-provider-composed.wasm.

Scalar / aggregate / table dispatch is a CBOR-envelope tunnel through linker.resolve-by-id + endpoint.invoke.

Host wiring

export DUCKLINK_SUB_EXT_BRIDGES="\
mobilitydb_network=$(pwd)/target/wasm32-wasip2/release/mobilitydb_network_duckdb_bridge_dynlink.wasm"

export DUCKLINK_SUB_EXT_PREBUILT="\
mobilitydb_network=$HOME/git/datafission/extensions/mobilitydb/deps/mobilitydb-network-provider-composed.wasm"

export DUCKLINK_SUB_EXT_ALIAS="\
mobilitydb_network=mobilitydb_network"

ducklink -c "LOAD mobilitydb_network;"

Regenerate

See the "Phase 9.2 mobilitydb per-sub bridges" section of SHIM-BRIDGES.md.

sqlink-shim-codegen \
  --dynlink \
  --target-dialect duckdb \
  --target mobilitydb_network \
  --provider-id mobilitydb_network-composed \
  --catalog ~/git/mobilitydb-shim-interface/mobilitydb-catalog.toml \
  --interface ~/git/mobilitydb-shim-interface/mobilitydb-interface.sqlite \
  --out ~/git/mobilitydb_network-ducklink-bridge

Do not hand-edit

Regenerate from the source-of-truth interface DB + catalog via sqlink-shim-codegen. Changes made directly here are lost on the next regen.