The thing it saves is appending a second (implicit session:Session) argument list to each method using the database. I have seen people being annoyed by it and trying to get rid of it multiple times. I understand this especially for writing larger DAOs. Using dynamicSession is not a good solution here. We should tell them a poposed way to do it. Moving the session into the surrounding class seems sensible to me. What do you propose? @freekh describes something similar in the play-slick docs https://github.com/freekh/play-slick/wiki/ScalaSlickTables

Maybe my example is simply not clear enough and may be altered to

val helper = (new Helpers)
import helpers._
execute(query)

instead of

(new Helpers).execute(query)