Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demo of dynamic/configurable/optionally remote proj.db file #422

Closed
wants to merge 3 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions REPRODUCE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
1. Generate proj.db

```c++
#include <stdio.h>
#include "spatial/src/spatial/proj/proj_db.c"

int main(void)
{
for (unsigned int i = 0; i < proj_db_len; i++)
putchar(proj_db[i]);
return 0;
}
```

g++ file.cpp -o generate_proj && ./generate_proj > proj.db


2. Launch http-server from the same folder where proj.db is

3. `python3 duckdb/scripts/run_tests_one_by_one.py ./build/release/test/unittest '/Users/carlo/duckdblabs/duckdb_spatial/test/sql/*`


TODO:

* Sort out context cleanup (see failure in unittester)
* Make location configurable via DuckDB option (should there be a MAP[extension_name] -> (MAP[option_name] -> option_value) to store extension options needed at load time ?
* Figure out whether proj.db should be fetched on load or anyhow proper strategy. Or maybe native have it backed in (who cares) but optionally configurable, and Wasm has it always remote
Loading
Loading