Philippe Rivière
Philippe Rivière
The error comes from DuckDB-wasm, the same happens on https://shell.duckdb.org/ We could fix the documentation by pointing to a different file, on a server that supports range requests, but that...
Issue referenced upstream; remains to be seen if we want to add a note in the documentation.
Looks like it's going to take a while before this can be fixed upstream in duckdb-wasm.
Similar issue here https://github.com/observablehq/framework/discussions/1747
*About the package size* Correlatively to the new features, this new release weighs a ton: the base files have doubled in size, and with the addition of extensions the binaries...
An alternative approach could be to publish a package on jsr or npm with the extensions we want to self-host.
*About the `LOAD` statements* Currently if several sql blocks use spatial functions (for example), you have to remember to type `LOAD spatial` in all of them, otherwise it's hard to...
The config option would indicate which extensions are self-hosted and where they're sourced from. Thus, they would be `INSTALL`ed from the self-hosted version. But `INSTALL` only tells duckdb where to...
Getting closer. TODO: - [x] configuration to allow the "core" and "community" keywords - [x] decide which extensions are loaded and which aren't (typically, "json" and "parquet" don't need to...
It's possible but difficult; my recommendation is to wait (a few days max) for the next release of Framework.