sea-query VS rust-postgis

The main limitation of prepared statement is that you can only insert values, so you cannot dynamically construct the query depending on the parameters. For that, you can use a query builder such as sea-query, which should handle that.

I would say https://www.sea-ql.org is your best bet. It’s highly configurable and they also have tools for no bs orm and graphql! Very new, but there is 1.0 release and tonnes of documentation and cook books.

[#508] Representing a identifier with &'static str. The IdenStatic trait looks like this:

🎉 We are pleased to release SeaQuery 0.27.0! Here are some feature highlights 🌟:

SeaORM or SeaQuery are also very good instead of diesel/sqlx

SeaQL.org was founded back in 2020. We devoted ourselves into developing open source libraries that help Rust developers to build data intensive applications. In the past two years, we published and maintained four open source libraries: SeaQuery, SeaSchema, SeaORM and StarfishQL. Each library is designed to fill a niche in the Rust ecosystem, and they are made to play well with other Rust libraries.

Upgrade sea-query to 0.26

As the new member of the SeaQL family, it's a stellar example of what could be done with Rust and the SeaORM / SeaQuery / SeaSchema suite of tools. We couldn't be more excited to see applications being built on Rust and the SeaQL ecosystem!

I'm curious about the Value enum & whether there is space on the roadmap to support custom types and maybe borrowed instead of owned values. I regularly use postgres-types ToSql and FromSql for simple enum variants, but have used things like postgis in anger before, so support for custom stuff would be awesome.