OCaml can do this with the PG'OCaml[0] library

0: http://pgocaml.forge.ocamlcore.org/

Awesome link, thank you.

That's kind-of what some ORMs try to do. Either the learning curve is too high, the ORM is too buggy, or someone screws something up and ends up writing software that's worse that just doing it the old-fashioned way.

Honestly, I'd rather that the DSL just import adapters for stored procedures; or that the language itself is modified to be more SQL-like.

Isn't this what, for example, Django models are? Or even js simpleschema?

Django models only work insofar as all clients are interacting with the database through django. If even one other path to the database exists, the django models become unreliable as a source of truth. With the profliferation of microservices written in different languages, it would be nice to have a cross-language, shared-service solution as simple as django models. Something like protobufs or JSON might work well, but ultimately you still need to write a messaging and persistence layer for them, so it's not as simple as just writing a few model files.

Basically every ORM does it. Django models, hibernate (java) as well for just 2 examples.

As far as I know, those only check at runtime (or when generating code), not at compile time.

What you mean by compile time, when we're talking Django and nodejs?

Yeah, that's part of my point. JS and Python can't even do what we're talking about here.

A lot of ORMs do this. In .net Entity Framework, you can define your schema entirely with classes, properties, and attributes and if your database doesn't match on startup then it will fail.

As well you can do migrations to match your database schema to your current code model when it changes.