book VS sqlx

Still finishing up on chapter 19 of the Rust book at https://doc.rust-lang.org/book/ !

Many people have already recommended the The Book which is a great resource that you should reference whenever you are stuck.

The Rust website links to some nice resources. I recommend the book called The Rust Programming Language.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

Read "the book" - https://doc.rust-lang.org/book/

there's no one i am literally no one except developers themselves know knows entire language ... then >>> https://doc.rust-lang.org/book/ <<< there's your entire rust language syntax and everything almost ; and i have read tons of things about rust and i coded in it ... plus i am reading documentation and i know what i am talking about i am not creating things out of air and even many rust developers dont like it because its too hard and its loaded with many stupid things , developers who coded in rust in many years ...

The Rust Programming Language Book

Read the first couple chapters of the The Rust Book. Maybe follow along with the exercises. But just let the intro sink in a bit.

To follow along with the demo and other content included in this guide, you should have a working knowledge of Rust. To learn more, you can read the book.

For beginner stuff there's a playlist by let's get rusty that goes over the book: playlist

sqlx

Thanks for sharing your experiences. I've been looking to get into snowflake for some time (even opened this https://github.com/launchbadge/sqlx/issues/986) . We thought to move to it years ago, but there's no way it was going to replace a significant amount of the mariadb we're running, and unless it did I wasn't looking forward to managing 2 DBs.

however, a much worse problem is its inability to do dynamic queries. If you have two queries that only differ in a column name, you're forced to copy paste the entire query. You can try and hack around it, but it's ugly either way. Here's a good overview, with no really good solutions.

Rust allows me to mainly only run the application to confirm things work from a business perspective.

For people starting out building stuff in rust - understand that there is a distinction of async code and libraries and can lead to confusing compiler errors if you don't realize there is a distinction. It's simple in hindsight but did cause me to waste hours barking up the wrong trees at first. Other wise just learn about `match` and Result/Option types asap, they're fundamental.

https://github.com/http-rs/tide tide is great to create an http server / routes

https://github.com/djc/askama I use this to template out HTML and it checks all my boxes, dynamic data, passing in functions, control flow.

https://github.com/launchbadge/sqlx sql interface for a variety of backend, async safe.

https://github.com/seanmonstar/reqwest http client to make requests

Rust is amazing, don't let the initial few speed bumps discourage you - building real things with rust is no more challenging today than any other modern language stack.

Perhaps Rust has some nice crates that will assist your development, but you're going to have to evaluate whether their design decisions meet the needs of your design, especially if you want to handle powerloss without data loss whilst maintaining high performance. Here's an example of where a create chose design over performance https://github.com/launchbadge/sqlx/issues/2007

SQLx's query macros act like format macros, and the database is apparently smart enough to not treat bind parameters as part of the SQL.

> Doesn't it need to run introspection queries to check the table structures?

Yes, but it can also run in 'offline' mode where it builds against saved metadata [0]

0: https://github.com/launchbadge/sqlx/blob/main/sqlx-cli/READM...