Custom getters with Global Database object removed

I’ve been trying Ktorm 2.7-RC that you uploaded after my request (thank you!).

In practice, I’ve found the new way of using Ktorm quite uncomfortable as now I’ve to pass around a database object. While this is doable, one place where I’ve been struggling with the new APIs is the custom setters. A while back you gave us an example of using a custom getter inside an entity interface:

interface Department : Entity<Department> {
    val id: Int
    val name: String
    val employees get() = Employees.findList { it.departmentId eq id }
}

Do you have an idea how to achieve this with the new API?

[vincentlauvlwj]

Yes, but then getList depends on the global db connection which means I wouldn’t have any control over running it on a different connection. Severely restricts the power of connection switching and, on a initial thought, in a way defeats the purpose of removing the global db object.

Yes, that’s exactly why I decided to remove Database.global. Here I just provide a workaround for you because you might want to use the global database like before.

[vincentlauvlwj]

I actually thought about doing that but I’d have to make it a lateinit var making it mutable from anywhere. Maybe I leave it like that or do something so that it can only be initialized once.

You can change the visibility of the setter, so that it can only be modified inside the kt file:

lateinit var globalDatabase: Database 
    private set