Stefan Zeiger

I just read the original ticket again and it is not what I thought it was. Integration of Plain SQL with the Lifted Embedding could be useful (and would indeed...

Workaround for composing queries in 3.1: ``` def concat(a: SQLActionBuilder, b: SQLActionBuilder): SQLActionBuilder = { SQLActionBuilder(a.queryParts ++ b.queryParts, new SetParameter[Unit] { def apply(p: Unit, pp: PositionedParameters): Unit = { a.unitPConv.apply(p,...

Another useful method: ``` def values[T](xs: TraversableOnce[T])(implicit sp: SetParameter[T]): SQLActionBuilder = { var b = sql"(" var first = true xs.foreach { x => if(first) first = false else b...

@wuservices there is no way to make this work with `tsql`. In order to perform the compile-time checking it needs to see the complete statement as a literal.

Proper integration blocked on #1263

Some thoughts about this: - Can we unify savepoint and transaction support so that you get a single combinator (e.g. `.atomic`)? The outermost one would create a transaction and if...

You can already name a DBIOAction. While this name won't show up in the SQL statement, it is printed to the log, which should make it easier to correlate it...

The monitoring integration probably won't happen. It would be nice if we could pass some sort of correlation ID through DBIOActions down to the threads that execute them. Maybe an...

Scheduling for 3.2 where we drop Java 6/7 support.

@xavier-fernandez An implementation would certainly be welcome, so if you're interested, please go ahead. You may want to look at https://github.com/tminglei/slick-pg and @tminglei probably has some ideas about it. Ideally...