Reactive Slick

Slick 3.0 has reached its first release candidate

JAX Editorial Team
Oil slick image via Shutterstock

The first release candidate for the next major version of the database query and access library Slick 3.0 is available right now. Builds are available for Scala 2.10 and 2.11 Scala on Maven Central.

Following the release of Slick’s 3.0.0-M1 milestone release last December, cited as the first step in ‘Reactive Slick’, Stefan Zeiger has announced Slick 3.0’s release candidate.

New major features

As befits a major release, the changes that fall into Slick 3.0 are substantial: In addition to a new API for the composition and execution of database operations, one can also find a new macro-based implementation of the Plain SQL API, with optional compile-time checking and type inference for embedded SQL statements.

In addition, Sick 3.0 now includes support for nested Option types and non-primitive Option types in the Lifted Embedding and many minor improvements and bug fixes in schema code generator.

Zeiger has stated that most of the manual accompanying this version has been updated, with the “Slick Testkit” and “Plain SQL Queries” chapters following soon. None of the standard Activator templates are available at the moment. They will be ported to 3.0 before the final release.

A few other points of improvement are as follows:

  • Support for the Reactive Streams API for streaming results from the database
  • Optional multi-line formatting and indenting of generated SQL code for more readable debug output
  • Improved configuration of database connections via Typesafe Config, including built-in support for HikariCP

The community has been encouraged to provide feedback on the stability of the release candidate if they encounter any problems, which should hopefully be sorted out in time for the release of the final version of Slick 3.0 within the next two weeks.

Over on Stack Overflow user brujoand had run into trouble when trying out Slick 3.0 while using IntelliJ IDEA, with Zeiger pointing out a known bug in IntelliJ’s presentation compiler – anyone using IntelliJ to play around should definitely have a look at the code here.

A list of the 80 amendments that have been implemented since version 2.1.0 can be found in the official release notes.

Comments
comments powered by Disqus