SQLite builds for WASI since 3.41.0
wasmlabs.dev
SQLite builds for WASI since 3.41.0
1–10 of 49 posts
Re: SQLite builds for WASI since 3.41.0
#2What would you use this for? I don't get the whole picture and the article doesn't talk about it.
Re: SQLite builds for WASI since 3.41.0
#3What would you use this for? I don't get the whole picture and the article doesn't talk about it.
Apparently they use it for their tests.
> We wanted to contribute upstream our patches for SQLite, as we were heavily relying on libsqlite for our tests of PHP.wasm with WordPress and Drupal.
Re: SQLite builds for WASI since 3.41.0
#4What would you use this for? I don't get the whole picture and the article doesn't talk about it.
Well, you can use it to access SQLite files in WASM runners, of course. So you get a portable, platform-independent piece of code that can run anywhere.
Although it was a bit of a surprise to see that they started out with the toy CLI tool that my self and Nicholas hacked on for a weekend (I wanted to be able to run SQLite commands in a-Shell, which is an excellent iPad CLI environment).
Re: SQLite builds for WASI since 3.41.0
#5> For legal reasons, we could not contribute directly (their patches)
What were the legal reasons?
Re: SQLite builds for WASI since 3.41.0
#6What would you use this for? I don't get the whole picture and the article doesn't talk about it.
So far the official WASM support from the SQLite project have only targeted WASM in the browser with a JS API. If I follow correctly this is about working with the SQLite team to upstream WASI support, which will eventually enable official support for it, and hence WASM on the server/cloud/edge and other WASI complement runners.
Re: SQLite builds for WASI since 3.41.0
#7What would you use this for? I don't get the whole picture and the article doesn't talk about it.
The file of my desktop app is a SQLite db in disguise, I could use this to open these files in a web version of my app, I suppose. I know there is a javascript implementation of SQLite out there but maybe this has better performance.
Re: SQLite builds for WASI since 3.41.0
#8> For legal reasons, we could not contribute directly, but we could discuss the required changes with someone from the SQLite team and then iterate with them by testing or commenting.
Ah, here's the catch! I knew SQLite didn't accept code contributions, I was suprised they managed to contribute anyway, and then this sentence clarified the situation. So they indeed did not manage to contribute their code itself, but the SQLite team agreed to write this code themselves. I wonder what was the SQLite team's motivation behind this cooperative work.
Re: SQLite builds for WASI since 3.41.0
#9> For legal reasons, we could not contribute directly (their patches) What were the legal reasons?
Looks like this: https://www.sqlite.org/copyright.html
Kind of weird, couldn't they use a CLA?
Re: SQLite builds for WASI since 3.41.0
#10> For legal reasons, we could not contribute directly (their patches) What were the legal reasons?
Most likely what is documented at https://sqlite.org/copyright.html
> SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution. In order to keep SQLite in the public domain and ensure that the code does not become contaminated with proprietary or licensed content, the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain.
> All of the code in SQLite is original, having been written specifically for use by SQLite. No code has been copied from unknown sources on the internet.
They want to be freaking sure they are the original authors / they can release the code in the public domain.
Public domain is tricky and does not exist in the same way everywhere. Where I live, you just can't decide to put something in the public domain, you need to use something like CC0 [1]
[1] https://creativecommons.org/share-your-work/public-domain/cc...