Based on slick documentation here: http://slick.typesafe.com/doc/2.0.0/schemas.html#tables it seems as if the way TableQuery was being constructed was wrong.

Using their recommended approach, making generic objects for the various operations becomes trivial. However, generic response objects break some code that was expected strong typed generic types.
Finished refactoring database access using singleton queries.

* Fixed an issue where I incorrectly formulated update requests as taking
a function rather than an entity.
* Removed a bunch of uneeded code.
* Changed error handling for some success cases to ensure that the save was truly successful.
Merge pull request #14 from bkyrlach/work

Database access refactoring to get rid of case class per entity anti-pattern.