I used Squeryl in my thesis (admittedly a while ago) and Slick[1] on a more recent project. Like you, I had ample experience in LINQ and it's definitely the feature I missed most from C#. I'm a fan of Slick.
I'm also looking forward to async SQL calls.
I've been building some Akka-based projects for a client and both they and I have been thrilled with the results. They're a startup that's gaining traction and they brought me in to help with scalability. I won't go so far as to say that Akka is a magic bullet but it makes reasoning about scalability far easier, though in our case we're mostly dancing around the IO bottleneck.
My GSOC project for this year is an extension to for comprehensions to enable LINQ-like conciseness without LINQ's inflexibility. If it ends up being merged into the compiler proper (a pretty big if), it should really help to make writing complex queries a lot less painful.
That's excellent. 9 of 14 proposed projects were accepted
http://www.scala-lang.org/gsoc2013
http://www.google-melange.com/gsoc/projects/list/google/gsoc... (type "scala team" in "Organization" box
Re:On Scala
by mynameisme on Wednesday June 19, 2013 @05:56AM
(#5904657)
Squeryl doesn't allow you to drop down to raw SQL, so I'd suggest avoiding it.
Re:On Scala
by papsosouid on Wednesday June 19, 2013 @10:24AM
(#5905685)
It is also rather broken, and the author doesn't appear to care. I'd second the suggestion to avoid it.
Another feature that got my attention was the ability to have a SQL framework that handled things similar to LINQ. I haven't tried it much yet, but Squeryl[1] has looked promising for being a Scala equivalent. I may have to look into Akka more though as that will easily take care of async SQLite calls as well[2].
[1] http://squeryl.org/introduction.html
[2] http://www.gamlor.info/wordpress/2012/05/async-sql-and-akka/