Since my original posting I went down that road (JdbcProfile) already and that seemed to make things worse. First, it locks in to a JDBC based driver which I’m trying to avoid. I’m okay with SqlProfile or RelationalProfile as those levels of abstraction I wish to retain. However, they are incomplete and so it is not possible to us them (e.g. can’t use a SqlProfile#Session to actually initiate a database session). In the case of using JdbcProfile, I get no definitions of Table[T] or TableQuery[T] when I import profile.simple._ into a trait. I’m sure all this is clear to you, but without release documentation it is very difficult to grasp .. even harder to extend. Rather than attempt to describe the difficulty I am having, I will work up an example and put it on github so it can be dissected there.
Thanks for helping me sort through this.
Reid.
> --
>
> ---
> You received this message because you are subscribed to a topic in the Google Groups "Slick / ScalaQuery" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/scalaquery/4Ns_J_8wbqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
scalaquery+...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.