No matter how you tackle this, your front end likely communicates in json and your database in sql.

At the crux of it, your backend has the job of translating between the two without openly exposing the database to the front end (unless security truly doesn't matter for your app)

There's no easy way to get around the fact you simply just have to write logic to mediate between those two languages.

The best way I use to avoid mismatch problems between BE<->DB is I use Code First Entity Framework Core as my ORM, letting my EF Core spec act as the source if truth fir my db schema via automated EF migrations.

This means the only way you get a mismatch is due to merge conflicts not being resolved properly if 2 devs both mutate the db schema at the same time.

C#'s Linq is also the closest first class API I have seen that very closely mimics sql.

I genuinely find Linq queries on Entity Framework easier to write and read than sql.