rusqlite VS cross

"Rusqlite is an ergonomic wrapper for using SQLite from Rust." - Crates.io

If you're less concerned about the "structure" of your data (e.g., serializing into rust types) and just need tabular data that can be queried (e.g., how much did we bet on X date, who placed a bet on Y team, etc.) I would definitely lean more towards a SQLite database for that kind of work. rusqlite can get you a functional database fairly quickly with a little reading of the documentation (be sure to use the "bundled" feature).

Create a connection per task. WAL is probably a good idea.

Even using SERIALIZED mode, sqlite has multiple APIs which are completely broken if two clients touch the same connection (https://github.com/rusqlite/rusqlite/issues/342#issuecomment...).

Don't bother, just don't share connections between threads and use the regular multi-thread mode (do use that though).

It fails your "ship with a crate" requirement, but when it comes to "csv but too small for a database" it's always worth having a think about SQLite. Of note, the rusqlite crate with the bundled feature will download, compile, and link against sqlite.

You may want to read the Readme of Rusqlite, especially the Optional Features.

As far as I know, the only option for an embedded SQL database is SQLite. The most actively maintained one, for rust, seems to be rusqlite (https://github.com/rusqlite/rusqlite).

Yes, but it's readonly. Also they did not merge loadable extensions support, which I need - https://github.com/rusqlite/rusqlite/pull/910

rusqlite 0.27.0, which looks like it's still the latest version

SQLite is written in C, while workers is based on V8 isolates, so it mainly runs JavaScript. Fortunately, it also supports running WASM through initialising and calling WASM modules via JavaScript. Emscripten can be used to build WASM from C, but I'd rather use it through Rust (using rusqlite), so this is what I focus on right away. Workers can also be written entirely in Rust using worker-rs.

To compile a program with musl on a glibc system you can use cross-rs!

I cross compile to Mac, bsd, windows, etc cross ... Works great for me with either docker or podman.

If docker is available for you, https://github.com/cross-rs/cross is another and reliable way to solve this kind of problem. I do use it regularly.

We are using https://github.com/cross-rs/cross.

There is some built-in support in rustc for cross-compiling, but getting the build to actually work can be tricky due to the need for an appropriate linker. Instead, we’re going to use the Cross crate, which used to be maintained by the Rust Embedded Working Group Tools group.

I have used cross before to cross compile from Linux to other Linux. It has a section on it's wiki about this. Maybe that could be of help.

You can use cross to build your application and copy the artifacts into an alpine armv7 container. It would also build faster due to using cross compilation rather than QEMU.

Looks like cross is the easiest way to get something cross-compiled but its Mac support is blocked behind building your own build image. Even that repo says that it might be broken.

Bonus: if you’re working with Rust and doing a lot of cross platform stuff, check out cross. It runs QEMU in docker so you can run tests on a bunch of different emulated targets easily- literally a one line setup, it’s kind of magical.

It's also not as naturally cross-compilable as Go, though that's partly a side-effect of not accepting being a semi-closed ecosystem to achieve that and cross exists as a stop-gap while things like cargo-zigbuild explore less drastic options.