如何避免 kotlin 上的 N+1 查询问题 暴露。(通过DAO的Reference.id.value字段获取值时)

Koy*_*nta 5 kotlin kotlin-exposed

我在 Kotlin JVM 项目上使用Exposed作为 O/R Mapper。(版本:0.17.6)

当我从 DAO API 获取外键列的值(由 Exposed 方法定义的列)时,我遇到了 N+1 查询问题reference

我用解决方法代码以某种方式解决了问题,但是有人知道正确的解决方案吗?

情况是这样的。

有两个表(users、user_addresses),一个表(user_addresses 表)在另一个表(user 表)上有外键引用。

object Users : LongIdTable("users") {
    val name = varchar("name", 30)
}
class User(id: EntityID<Long>) : LongEntity(id) {
    companion object : LongEntityClass<User>(Users)

    var name by Users.name
}

object UserAddresses : LongIdTable("user_addresses") {
    val user = reference("user_id", Users)
    val address = varchar("address", 30)
}
class UserAddress(id: EntityID<Long>) : LongEntity(id) {
    companion object : LongEntityClass<UserAddress>(UserAddresses)

    var user by User.referencedOn(UserAddresses.user)
    var address by UserAddresses.address

    fun toRow(): UserAddressRow {    
        return UserAddressRow(
            id.value,
            user.id.value,
            address
        )
    }
}

data class UserAddressRow(val id: Long, val userId: Long, val address: String)
Run Code Online (Sandbox Code Playgroud)

当我尝试 get 时List<UserAddressRow>,出现了 N+1 查询问题。我发现当我调用 时Reference.getValue,SELECT 查询在下面的点上执行。 https://github.com/JetBrains/Expose/blob/master/expose-dao/src/main/kotlin/org/jetbrains/expose/dao/Entity.kt#L129

@Test
fun test() {
    transaction {
        UserAddress.all().map {
            it.toRow()
        }
    }
}    
Run Code Online (Sandbox Code Playgroud)

测试数据

INSERT INTO users (id, name) VALUES (1, 'A');
INSERT INTO users (id, name) VALUES (2, 'B');
INSERT INTO user_addresses (user_id, address) VALUES (1, 'X');
INSERT INTO user_addresses (user_id, address) VALUES (1, 'Y');
INSERT INTO user_addresses (user_id, address) VALUES (2, 'Z');
Run Code Online (Sandbox Code Playgroud)

SQL查询日志(公开的调试日志)

[] 2019-11-22 10:41:55.656 [main] DEBUG [cid- uid--] Exposed - SELECT user_addresses.id, user_addresses.user_id, user_addresses.address FROM user_addresses
[] 2019-11-22 10:41:55.668 [main] DEBUG [cid- uid--] Exposed - SELECT users.id, users."name" FROM users WHERE users.id = 1
[] 2019-11-22 10:41:55.670 [main] DEBUG [cid- uid--] Exposed - SELECT users.id, users."name" FROM users WHERE users.id = 2
Run Code Online (Sandbox Code Playgroud)

如果我使用readValue而不是user.id,问题就解决了。我不确定这个解决方法是否正确。请帮我。

   fun toRow(): UserAddressRow {    
        return UserAddressRow(
            id.value,
            readValues[UserAddressTable.user].value,
            address
        )
    }
Run Code Online (Sandbox Code Playgroud)

Koy*_*nta 1

我注意到下面的简单模式效果会更好。

//Define userId column in DAO (UserAddress class), and use it
class UserAddress(id: EntityID<Long>) : LongEntity(id) {
    companion object : LongEntityClass<UserAddress>(UserAddresses)

    var user by User.referencedOn(UserAddresses.user)
    var userId by UserAddresses.user
    var address by UserAddresses.address

    fun toRow(): UserAddressRow {
        return UserAddressRow(
            id.value,
            userId.value,
            address
        )
    }
}

//There is only one SQL statement executed
//SELECT user_addresses.id, user_addresses.user_id, user_addresses.address FROM user_addresses
Run Code Online (Sandbox Code Playgroud)