Richard Dallaway

See also: https://stackoverflow.com/questions/49838709/slick-pass-in-column-to-update/49873298#49873298

Relates to: #163

If it's the problem I think it is, we've worked around this in _Essential Slick_ by just using bold: ``` **Group By True** There's a `groupBy { _ => true}`...

Also for running string extension methods on optional strings: https://stackoverflow.com/a/45409859/154248

NB: as Slick 3.3.0, there's a mapping in place for string extension methods. E.g., if your column is an `Option[String]` you can now just `like` that or whatever. Fact check...

See also: https://stackoverflow.com/a/65320259/154248

This feels like a resonable way to resolve this: https://github.com/d6y/plain-in

See also: https://github.com/tarao/slick-jdbc-extension-scala/

Relates to: #114

We should also mention you can define projections for each type you want to nest. Here's an example: ``` scala def * = (name, address) (Person.tupled, Person.unapply) def name =...