A modern programming language that makes developers happier.

kotlinlang

I think both db-first and code-first approaches should be supported. Sometimes you have a db and need to interact with it. Sometimes you have more freedom in what you can do with db, especially when prototyping and there is no need to maintain, migrate, and validate the scheme against various external conditions. However, I think db-first can be done with Exposed-style definitions, but instead of creating/updating scheme, just perform a validation pass. It’s mostly first-time generation of Exposed Table classes that is needed in this case. Could be a command-line tool or something. Almost all the code is there to read the schema, because it does diff.