The model organisation is completely up to you. For example, I like to
have a some model classes in different files, each file representing a
"context", for example, Person.scala, would have Person, Address,
HairColor etc.
You can definitely have utility methods in the model classes. For
example, suppose you have a column `yearOfBirth` your Student class,
you could have a method `isAdult`, like:
def yearOfBirth: Column[Int] = column[String]("Stud_yob")
def isAdult: Column[Boolean] = (2015 - yearOfBirth) >= 21
Now you can query `students filter { _.isAdult }`.
Cheers
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Slick / ScalaQuery" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
scalaquery+...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/scalaquery/79fcc255-8c20-4ca7-9e20-d7687aa41c32%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.