DAO Architecture

[FelixStumvoll]

I am currently trying out this library but i'm a bit curious how an architecture with the rich domain model/DAO would look like.
for example i want create a new entity but before i would like to validate the data. in a standard service->dao->db architecture i would do this in the service layer.
however i'm not quite sure how i would do this with the exposed daos.

[sunqitao]

class PersonService {
companion object{
fun getTopUser():List{
val userList = ArrayList()
transaction {
val res = Users.selectAll().limit(5)
res.forEach {
userList.add(User(id = it[Users.id],name =it[Users.name],email = it[Users.email] ))
}
}
return userList
}
}
}
object Users:Table("user"){
val id = long("id").autoIncrement()
val name = varchar("name",length = 64)
val email = varchar("email",length = 64)
}
data class User(val id:Long,val name:String,val email:String)

[sunqitao]

User： entity
PersonService：service
Users ： Dao

[FelixStumvoll]

ok so you are splitting up the DAO and the Entity in two seperate classes

[sunqitao]

ok so you are splitting up the DAO and the Entity in two seperate classes

yes

[bog-walk]

For future reference, here are links to some opinions on DAO setup and key issues to track regarding DAO entities:

• GH issue Support natively data classes + repository based DAO #24
• GH issue Proper way to serialize/deserialize DAOs entities. #497
• EXPOSED-463