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

Ability to open a SQLite database by "uploading" it #13

Open
simonw opened this issue May 2, 2022 · 4 comments
Open

Ability to open a SQLite database by "uploading" it #13

simonw opened this issue May 2, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@simonw
Copy link
Owner

simonw commented May 2, 2022

Not actually uploading it to the server, but opening it through the browser file open UI - like https://squoosh.app/

@simonw simonw added the enhancement New feature or request label May 2, 2022
@simonw
Copy link
Owner Author

simonw commented May 2, 2022

Related:

@psychemedia
Copy link

In this general space (getting content into a browser based app), you could also add file system access.

Elsewhere, JupyterLite was the prompt for the jupyterlab-contrib/jupyterlab-filesystem-access extension, I think.

@jsmarr
Copy link

jsmarr commented Jan 11, 2023

Related: It looks like you can't use a file:/// URL to load a local sqlite db into datasette lite, which I imagine is a common use case. If someone sends you a .db file to use, you need to find a "real URL" to host it at, which may not always be easy/desirable, esp. if it's sensitive data. Wonder how much work it would be to support file:/// URLs, whether or not it comes with a "nice file picker UI" to figure out the URL (which of course would be even nicer).

@jsmarr
Copy link

jsmarr commented Jan 11, 2023

As a workaround, I used the "Web server for chrome" extension to start a local web server, which also lets you explicitly set CORS headers, which seem to be working. But when I try to use the resulting URL, which loads fine in my browser and looks like http://127.0.0.1:8887/path/to/file.db it still says "That database URL could not be loaded" with no other explanation or error in the console log. Not sure why it's not working or how to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants