mobilitydb-ducklink-bridge

Generated by sqlink-shim-codegen from mobilitydb-interface.sqlite with --target duckdb.

Do not edit by hand — regenerate from the interface DB.

Step 4 status

This bridge is a scalar-first cut (Step 4 of PLAN-shim-codegen-datalink-migration). Scalars are wired end-to-end against the duckdb:extension@2.2.0 contract; aggregates / table functions / pragmas / casts return Duckerror::Unsupported. The verification gate at Step 4 is that the crate cargo build --target wasm32-wasip2 --release cleanly — full smoke-tests against a ducklink runtime are deferred until ducklink-loader gains the wit-value lift the SQLite-target wires via sqlink-loader (#559).

Surface from the interface DB

extension	version	scalars	aggregates	UDTFs	windows	types	operators	casts	preprocessors	catalog	indexes
mobilitydb	0.1.0	720	30	43	0	78	32	36	1	0	0

Build

cargo build --target wasm32-wasip2 --release

The build needs wit-bindgen and an installed wasm32-wasip2 target (rustup target add wasm32-wasip2).

Compose with the upstream shim wasm

The DuckDB target composes the same way the SQLite target does — wac plug the upstream <primary>-composed.wasm into this crate's wasm, then a ducklink-loader integration step (deferred) loads the composed artifact.

wac plug \
  --plug ~/git/mobilitydb-wasm/mobilitydb-composed.wasm \
  -o mobilitydb-ducklink-loadable.wasm \
  target/wasm32-wasip2/release/mobilitydb_ducklink_bridge.wasm

Regenerate

cd ~/git/sqlink-shim-codegen
cargo run --release -- \
  --target duckdb \
  --interface /path/to/mobilitydb-interface.sqlite \
  --out ~/git/mobilitydb-ducklink-bridge

License

Apache-2.0.