sqlx

It's available to some in extend in rust, e.g. SQLX [1] allows you to typecheck queries. [1] https://github.com/launchbadge/sqlx

SQLX has entered the chat [1]. [1] https://github.com/launchbadge/sqlx

Like Rust's Sqlx? https://github.com/launchbadge/sqlx

SQLx [1] is commonly recommended. It has the nice feature that your queries can be verified at compile time. [1]: https://github.com/launchbadge/sqlx

I have been asking this myself for a while now, I generally do enjoy writing SQL, but I also get the feeling that it's not suitable for building applications. So why is there no "functional" query language? Something like Haskell, but for databases. You would get the benefits of a declarative model, composeability and type-safety. I am currently using sqlx[1] and it's great in terms of type-safety, but you can't compose queries. I don't like to use ORM's, they are usually good for simple things, but hard things are impossible and you have to use/understand SQL anyways. [1] https://github.com/launchbadge/sqlx

https://tourofrust.com/ is fun. Learning rust has a weird initial learning curve dealing with the aggressive analyzer/compiler and how you have to approach your variables, but after that initial hump it is one of the coziest languages I've used. Having what was initially a bit of a nag, is now a godsend when i'm getting red-squiggles in vscode for a typo in my SQL string for a misnamed column, or a field in my template was removed and so my struct shows how it's now unused. 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 u

> 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...

I felt the same way until I found sqlx (https://github.com/launchbadge/sqlx). The package lets you write sql in your app with compile-time checks. Was so much easier to get up and running than learning a new ORM.

If writing SQL directly, what process do you use to update your queries during schema changes? Do you rely on a test suite to catch errors then update queries by hand? Are you using compile-time checks through libraries like sqlx [1]? [1]: https://github.com/launchbadge/sqlx

Part of the solution could be using tooling which can compile time check SQL is valid like https://github.com/launchbadge/sqlx

On a similar note, there's also sqlx for rust [1] - and I find it extra impressive that they manage to support not only postgres, but sqlite and and mysql too. [1] https://github.com/launchbadge/sqlx

There's an offline feature that > Enables building the macros in offline mode when a live database is not available (such as CI) [0] [0] https://github.com/launchbadge/sqlx/blob/76ae2865005cc79d569...

I find that the best of both worlds is to use something like sqlx for rust [1], which does compile time checking (using postgres explain analyze!) of the queries and macros for static typing, but still let you write the query raw (and can be turned off completely by removing the trailing macro `!` as an escape hatch) We use it extensively for Windmill (e.g: [2]) and couldn't be happier. [1]: https://github.com/launchbadge/sqlx [2]: https://github.com/windmill-labs/windmill/blob/d60a770eb710e...

ORM's come and go just like web frameworks, so I really don't care for them. I use sqlx [1] when I can. 1: https://github.com/launchbadge/sqlx