HeidiSQL VS sqlx

HeidiSQL is used to show database changes, consider supporting it.

HeidiSQL is also a lightweight SQL client that supports a long list of databases including MariaDB, MySQL, MS SQL, PostgreSQL, SQLite, Interbase and Firebird. In addition to basic SQL client functionalities, users can export structures and data to SQL files or copy them to the clipboard or other servers.

Aye! The ability to quickly debug complex persistent data using GUI tools is another plus. (I have used HeidiSQL for this, just because I already had it installed and it also supports SQLite.)

simple google search, first link: https://github.com/HeidiSQL/HeidiSQL/issues/830

If HeidiSQL is right for you, you can download it here and follow updates on their GitHub page.

What exactly are you missing? I haven't really written "boring corporate backend stuff" in a few years but something like sqlx provides everything I've ever needed there.

Badges are the little rectangles you typically see at the top of a crate's README: https://github.com/launchbadge/sqlx/blob/main/README.md

SQLX has entered the chat [1].

[1] https://github.com/launchbadge/sqlx

Database : SqLite (using sqlx).

The current (well, removed) MSSQL sqlx driver also doesn't support encrypted connections (https://github.com/launchbadge/sqlx/issues/1552), so it might work locally on an unnamed instance but not over the network until they add in the newer driver (which will be closed source but for an OSS project you should be able to request a free license I think)

I'm considering making my own wrapper over lower-level database drivers. There are a lot of features in sqlx that I don't need, and the latest version seems to have removed useful data structures that SQLPage is using. It also removed support for SQL Server.

add Ed25519 to AuthPlugin enum on https://github.com/launchbadge/sqlx/blob/061fdcabd72896d9bc3abb4ea4af6712a04bc0a8/sqlx-core/src/mysql/connection/auth.rs and implement them using these crates: