Any way around having duplicate data classes and table objects?

[Aditya94A]

Noticed this pattern in Exposed as well and I think this really adds a lot of friction and overhead to using such a solution.

Does kdbc offer a work around for this?

[edvin]

That was my initial goal, but I was unable to find an elegant solution without resorting to annotations and other ugliness. In practice there is very little friction/overhead in doing it this way though, so I concluded that it wasn't worth chasing any further.