pull_requests: 1031503844

This data as json

id node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association repo url merged_by auto_merge
1031503844 PR_kwDOBm6k_c49e3_k 1789 closed 0 Add new entrypoint option to `--load-extension` 15178711 Closes #1784 The `--load-extension` flag can now accept an optional "entrypoint" value, to specify which entrypoint SQLite should load from the given extension. ```bash # would load default entrypoint like before datasette data.db --load-extension ext # loads the extensions with the "sqlite3_foo_init" entrpoint datasette data.db --load-extension ext:sqlite3_foo_init # loads the extensions with the "sqlite3_bar_init" entrpoint datasette data.db --load-extension ext:sqlite3_bar_init ``` For testing, I added a small SQLite extension in C at `tests/ext.c`. If compiled, then pytest will run the unit tests in `test_load_extensions.py`to verify that Datasette loads in extensions correctly (and loads the correct entrypoints). Compiling the extension requires a C compiler, I compiled it on my Mac with: ``` gcc ext.c -I path/to/sqlite -fPIC -shared -o ext.dylib ``` Where `path/to/sqlite` is a directory that contains the SQLite amalgamation header files. Re documentation: I added a bit to the help text for `--load-extension` (which I believe should auto-add to documentation?), and the existing extension documentation is spatialite specific. Let me know if a new extensions documentation page would be helpful! 2022-08-19T19:27:47Z 2022-08-23T18:42:52Z 2022-08-23T18:34:30Z 2022-08-23T18:34:30Z 1d64c9a8dac45b9a3452acf8e76dfadea2b0bc49     0 5a2a05f2cea7b55b1c3bb1df043c0a454eca6563 663ac431fe7202c85967568d82b2034f92b9aa43 CONTRIBUTOR 107914493 https://github.com/simonw/datasette/pull/1789    

Links from other tables