User(id: Int), Game(id: Int), UserGame(gameId: Int, userId: Int)

users.games()

game.members()

@KomapperEntity
@KomapperOneToMany(UserGame::class)
@KomapperAggregateRoot("users")
data class User(@KomapperId val id: Int)

@KomapperEntity
@KomapperManyToOne(User::class)
@KomapperManyToOne(Game::class)
data class UserGame(
    @KomapperId val gameId: Int,
    @KomapperId val userId: Int
)

@KomapperEntity
@KomapperOneToMany(UserGame::class)
data class Game(@KomapperId val id: Int)

context(org.komapper.core.dsl.query.EntityStoreContext)
fun User.gemes(): Set<Game> {
    return this.userGame().mapNotNull { it.game() }.toSet()
}

context(org.komapper.core.dsl.query.EntityStoreContext)
fun Game.members(): Set<User> {
    return this.userGame().mapNotNull { it.user() }.toSet()
}

val store: EntityStore = db.runQuery(...)

with(store.asContext()) {
    val users: Set<User> = store.users()
    for (user in users) {
        val games: Set<Game> = user.gemes()
        for (game in games) {
            val memabers: Set<User> = game.members()
        }
    }
}

store: EntityStore

with(store.asContext())

val user = db.runQuery(...)
val userGames = user.games()

Is it planned to simplify the usage of this API also ?

Or even just extension val properties if it’s not doing any transaction internally

.games

.games()

Just using

.games

of

.games()

, as in Kotlin we rarely use methods for returning a value except when it does some internal computing

data class User(val id: Int) {
    companion object: EntityMetadamodel<User, Int, Companion> {
        ...
    }
}

QueryDSL.insert(User)

QueryDsl.insert(Meta.user)

QueryDSL.insert(User)