Allow user to override range requirement

[llimllib]

relates to #157

In development, I use devd, which does not support range requests, and have a small data set. It would be very useful for me to be able to disable the range support requirement while I'm in development; my production server supports them.

The inability to turn this off means if I want to use duckdb-wasm, I have to rewrite my whole development setup.

[ankoh]

I understand your point. I was just not quite sure about the negative effects of a default fallback to non-ranged fetches.
The problem is, that duckdb-wasm runs in a web worker.
So if your user expects ranged reads and we would fallback to full reads for whatever reason, we might end up blocking the database until the entire file is downloaded.
This is quite problematic especially for large files.

[ankoh]

It is non-trivial to abort downloading such a file once we started. We can terminate the web worker but thats about it (without SharedArrayBuffers).
This will change as soon as DuckDB gets fully async I/O but that's not possible today.

[ankoh]

We could add something like allowFullHTTPReads to the DuckDBConfig that defaults to false, for now.

[llimllib]

that would be the ideal solution for me, if it doesn't make sense overall feel free to close this though

[ankoh]

@llimllib Please try version 0.1.12-dev26.0 , it automatically falls back to full requests.
We only log a warning to the console for now.

[ankoh]

Neat side effect:
The shell can now read files from servers that dont include range in the CORS header Access-Control-Allow-Headers.

[llimllib]

Can confirm it works, thank you very much!