rusqlite VS cross

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.

For the persistence layer I used Rusqlite and r2d2-sqlite for creating a connection pool.

There are feature flags in chrono that make possible to disable usage of time: https://github.com/rusqlite/rusqlite/pull/1031

I want to use arrays in sqlite but the documentations for rusqlite doesn't have examples of how to use the extra array feature. How do I store and search text arrays in rusqlite?

Since this is a learning project, its probably not a good idea to count on this being production ready. If you need SQLite in your project checkout rusqlite. And for cross compiling issues simply use its bundled feature, makes it a breeze.

I build on x86, for aarm64/armv7 musl targets, using cross-rs. My issue is, forever and always, tls. Previously I just used openssl = { version = '0.10', features = ["vendored"] } in Cargo.toml.

A Docker-based solution like cross is generally suggested because the ad-hoc nature of C and C++ build systems can impart an unpredictable level of difficulty on cross-compiling any C or C++ libraries your Rust code depends on.

Have you tried using cross?

cross-rs (https://github.com/cross-rs/cross)

Yes, cross compiling with https://github.com/cross-rs/cross is relatively painless. I recommend doing that instead of compiling on the PI.

I develop on x86, and when targeting other platforms, I use cross-rs to compile, the applications are always deployed on Docker containers, using either ubuntu:22.04, or alpine:3.17 as the Base (to x86, armv6, or arrm64 targets, depending on the project).

Way to reproduce: 1. Create a new project 2. Add compress-tools = "0.14" to Cargo.toml 3. Install docker and cross-rs 4. Create Cross.toml with content [target.armv7-unknown-linux-musleabihf] pre-build = ["DEBIAN_FRONTEND=noninteractive apt-get -yq install libarchive-dev protobuf-compiler"] 5. Run cross build --release --target armv7-unknown-linux-musleabihf

As for inspiration, look no further than cross.

I strongly recommend trying to use cross https://github.com/cross-rs/cross it should work fine for you use case, it not only takes care about compiler/linker but also external libs you might link against. If a lib is missing you can make you own dockerfile and install it in the target sysroot you are compiling then against.

Have you seen cross? I don't normally do multi-platform builds, but I've used it for compiling for different arches. For me if there's nothing major dynamically linked then it "just works(TM)". If you do need to link to something like SQLite then you can setup your own base image that provides it (the "Custom Docker image" section)