teloxide VS rusqlite

I'm using teloxide, which is a crate for building Telegram bots. I have a small Telegram bot running on my Raspberry Pi, and since it's very slow to compile, I'm trying to cross compile it from my Windows machine, with no luck.

I do completely agree with your advice of using `Arc`s. But unfortunately, sometimes it gets very tedious to deal with all these `Arc`s: https://github.com/teloxide/teloxide/blob/ec1d41220c51872cf9....

It also blurs the advantage of Rust as a lifetime validation tool if you use reference counting anyways. But it seems that it's the only viable approach for async at the moment.

A Telegram bot built with Rust Telegram bot framework Teloxide, used to provide support to new users discovering our network, and to help them navigate through our channels of information by using various commands to interact with and find a job as fast as possible without need for visiting /jobs page from our website.

There is https://github.com/teloxide/teloxide though, maybe there is a confusion? It's actively maintained?

This is prototype and we plan to include more features. The bot is built with Rust Teloxide framework and we plan to deploy more Rust code for our production code, web pages and end points.

We also built a Telegram bot with Rust Teloxide framework and will deploy this week and show that is is written in Rust also.

Working on teloxide, a Telegram bots framework for Rust.

As was said earlier, for visibility purposes, gRPC client is also a Telegram bot. To implement the bot, teloxide library was used.

You can also make some social media bots with Rust

"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