Jan Christopher Vogt

@i-schuetz are you suggesting ``` scala // unmodifiable traits from library trait CatDao { def save(input: Cat): Future[Cat] } trait DogDao { def save(input: Dog): Future[Dog] } // implementation class...

@i-schuetz nothing wrong with it, sounds like a good way to go in such a case. Not sure you can't construct an example where this breaks down, but I don't...

@szeiger I heard these troubles of the migration being a bit rough for some projects multiple times. how hard would it be to support or write a gist to allow...

As this seems to be a common migration problem, I support the integration of this feature. Probably it should be documented that this is not the recommended way to use...

@schmitch Do you have time to add it do the docs? You can submit a PR against: https://github.com/slick/slick/tree/master/slick/src/sphinx (Remember Slick is an open source project with some, but limited commercial...

Not supported out of the box, but would be nice to have. The way to go would probably be creating an instance of Slick's Model classes from a Table class...

Slick doesn't have a feature for generating DDL for views. Sounds like a nice contribution if you want to give it a shot, but also seems like it would require...

You can do something along these lines: https://github.com/slick/slick/blob/408f2e55aa0a7553a445c83b7ee5ef159f805694/slick/src/main/scala/slick/jdbc/StaticQuery.scala#L93 We should document and maybe ship a small wrapper around. maybe a good TODO for @trevorsibanda this summer

@lisinge could you turn this into a PR that allows us to see the error in CI ?

@radsaggi maybe you have time to look at these? @szeiger is the expert in the area though