rust-mysql-simple
metrics
rust-mysql-simple | metrics | |
---|---|---|
3 | 19 | |
647 | 70 | |
- | - | |
6.6 | 9.7 | |
17 days ago | 6 days ago | |
Rust | ||
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-mysql-simple
- What would I need to use in order to interface with a database?
-
Diesel 2.0.0 RC1
We use libmysqlclient mostly for historic reasons. The mysql crate did just not exist back then when diesel started and rewriting all the internal code now is just something that we did not have the time nor motivation for. That written: Diesel is designed in such a way that connections can be provided by third party crates, even for existing backends. Diesel 2.0 adds explicit documentation for this as part of the connection trait and we are definitively interested to see pure rust implementations for the postges and mysql backend there. Also there is this discussion in the rust-mysql crate repository about a potential diesel integration. If someone is interested in working on this (or the equivalent implementation for postgresql), please reach out to us. We definitively can provide some pointers where to look for stuff and how to generally approach such an implementation. It's likely nothing that's really hard, it just requires someone to spend some work on it.
-
Reviews of the Diesel ORM, are there better alternatives?
I can understand that this can be frustrating and I know that the situation there is not ideal for diesel. There are certainly things to improve there by either providing a bundling support which builds the native library as part of the normal build process or by implementing a pure rust connection implementation. Both is possible with diesel, but requires some work. At least the pure rust connection implementation is something that can be provided by a third party crate now with upcoming diesel 2.0 release. If you are interested in that checkout this and this issue. As for the bundling support: This requires changes in the mysqlclient-sys and pq-sys crates. Again help there is welcome. In the end it makes me sad that some people have repeating decided that a solution to this problem is to write just another crate instead of helping to fix these issues. This just results in everyone have more work to do, as there are now two non-perfect solutions instead of having one slightly improved solution.
metrics
-
SQLx 0.7 released! Offline mode usability improvements, performance fixes and major upgrades across the board!
It's worth keeping an eye on Diesel's metrics suite (https://github.com/diesel-rs/metrics) as well; I found and fixed some suboptimal buffering that was affecting performance.
-
What's everyone working on this week (26/2023)?
See here for some numbers. The relevant code lives inside the diesel github repository. Please also keep in mind that these are just numbers and you should run those these on your own and also run tests with your actual work load.
-
Sqlx, diesel, orm or other sqlx query ?
Performance is worse than in comparable frameworks
-
Handle sessions and database requests
For the database part you might want to checkout a crate that's not based on sqlx as sqlx is known for providing non-optimal performance for the sqlite backend. rusqlite or diesel perform much better for this use case.
-
What ORM do you use?
No it will likely not be less performant. See these numbers for some benchmark results for numbers. (As always with benchmarks: Please don't trust my numbers. To be sure you need to do your own benchmarks with your own use-case)
-
Trying to learn by tutorials, for cannot find a single Actix/Diesel tutorial that actually compiles
See here for some benchmark results. The benchmarks itself are in the diesel repository. Otherwise I believe there are numbers in the techempower benchmarks as well, although that includes other factors .
-
Thoughts about switching from sqlx to tokio_postgres?
I'm developing a Rust web server backend in Axum that uses Postgres and performance will be pretty important since I plan to run it on one server for as long as possible. It seems like the postgres crate is about 2x faster than sqlx, and the postgres repository seems pretty active still.
-
Ormlite: An ORM in Rust for developers that love SQL
Congratulations to the release. I know all of this is hard work. I would like to invite you to submit a ormlite implementation to the diesel benchmark collection. As soon as that's merged you will get regular reports here. The relevant code is here in the diesel repository.
-
Rails developers write some Rust: a review of Axum 0.6
In that case you may be interested in the metrics for different database libraries. diesel is doing rather well at the moment. sqlx is in the middle of a large rewrite that should improve performance, so we'll see how it compares after that
-
Using Rust as my Backend
See here for some benchmark results for the diesel repository. Please keep in mind that as always with benchmarks, these numbers are not necessarily true for your usecase. Be sure to checkout at least the benchmark code and draw your own conclusions from there.
What are some alternatives?
mysql_async - Asyncronous Rust Mysql driver based on Tokio.
sea-orm - 🐚 An async & dynamic ORM for Rust
mysql-proxy-rs - A highly scalable MySQL Proxy framework written in Rust
sea-query - 🔱 A dynamic SQL query builder for MySQL, Postgres and SQLite
r2d2 - A generic connection pool for Rust
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
cornucopia - Generate type-checked Rust from your PostgreSQL.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
rust-postgis - postgis helper library.
tikv - Distributed transactional key-value database, originally created to complement TiDB
const-eval - home for proposals in and around compile-time function evaluation