A modern programming language that makes developers happier.

kotlinlang

Another good feature would be the ability to ignore certain fields when loading data into the entity. My use case is that in the unit tests, I need to insert into the table test data and there are fields that are not nullable that I don't need when retrieving data for the production code... Maybe an extra parameter in the KomapperColumn annotation `forWritingOnly` (naming could be different...)?

To manage two copies of the same entity for read/write wouldn't be too nice, since there's more chance for error unless the entity checking feature would exist...

Of course, these fields would have a default value so that they can be loaded without effecting the readable ones.

(Or maybe instead of adding this to `@KomapperColumn` , it could be added to `@KomapperIgnore`  which would probably be much cleaner...)

like `@KomapperIgnore(ignoreForReading=true)`

Your use case appears to be specific and may not be a good fit for inclusion in Komapper. Perhaps you could develop a tool to handle your own annotations?