sea-query VS river

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!

More info on the wiki https://github.com/riverwm/river/wiki

Here is the related github issue

If you can get past some minor wayland related annoyances, river is pretty easy imo, you can write a config in whatever format you want, it just needs to be an executable file, the most common type is a shell script. The actual configuration happens by calling the riverctl program from the file, which from what I've heard is a similar method compared to bspwm.

Coming from awesome you may find river more to your liking than sway.

River crashed everytime I closed Chromium. The developer fixed it in 5 minutes :)

I've written a plugin that implements the river-layout-v3 wayland protocol in Hyprland. This means you can run something like rivertile, river-luatile, rivercarro or kile as a layout provider.

Author here. And yeah, as of 0.6.0 it supports master stack - I just called it stack main. I was in fact inspired by river: https://github.com/riverwm/river. River is really promising but is still in very early development. Sway on the other hand has been around for a long time and I, for now, prefer that stability.

In my very specific case, I'd probably start by taking a look at how animations were previously implemented in river, and then I'd pay careful attention to that transform matrix at the end. I'm not super crazy about the implementation using timers to drive it (versus interpolating where the transform should be across a deadline), but I guess they were going for smoothness.

riverwm wayland compositor