A modern programming language that makes developers happier.

kotlinlang

And if there's contradicting definitions in one of the DTOs compared to another, will there be an error or will Komapper quitely create one of them arbitrarily...?

It seems like in the situation I came across I had two entities (in two packages but on the same Meta object) with the same table/name etc... one WITH field X and the other w/o it, and Komapper for some reason was using the one w/o the field when using Meta.all() in QueryDSL.create...

`Meta.all()` returns all metamodels in no guaranteed order. `QueryDSL.create/drop` ignores already-exists-exceptions. If there are multiple metamodels for the same table, you may want to filter them and then run `QueryDSL.create/drop` for them.

&gt; `QueryDSL.create/drop` ignores already-exists-exceptions.
Maybe it should try ALTER TABLE on an existing table that doesn't have all the fields in the other DTOs...?

We do not believe that is Komapper’s responsibility.