Skip to content

Latest commit

 

History

History
122 lines (100 loc) · 3.83 KB

MIGRATION.md

File metadata and controls

122 lines (100 loc) · 3.83 KB
Raw

Migration to 1.1.x

Version 1.1.x removes Play.current dependency (deprecated in play 2.5). Database configuration is now resolved using DI. To fully use DI some major changes in class composition are required. Entity definition can be in separate file, but all classes that depends on Database Driver have to be mixed together.

Changes in Entity ID class definition: Old way:

import LongUnicornPlay._
case class UserId(id: Long) extends BaseId

New way (explicit ID type):

import LongUnicornPlayIdentifiers._
case class UserId(id: Long) extends BaseId[Long]

Table definition: Old way (global import):

import LongPlayUnicorn._
import LongPlayUnicorn.driver.api._

class UserTable(tag: SlickTag) extends IdTable[UserId, User](tag, "test") {
  def name = column[String]("name")
  override def * : ProvenShape[User] = (id.?, name) <> (User.tupled, User.unapply)
}

class UserRepository extends BaseIdRepository[UserId, User, UserTable](TableQuery[UserTable])

New way (Mixed Unicorn object):

trait UserRepositoryComponents {
  self: UnicornWrapper[Long] =>

  import unicorn._
  import unicorn.driver.api._

  class UserTable(tag: SlickTag) extends IdTable[UserId, User](tag, "test") {
    def name = column[String]("name")
    override def * : ProvenShape[User] = (id.?, name) <> (User.tupled, User.unapply)
  }

  object UserBaseRepository extends BaseIdRepository[UserId, User, UserTable](TableQuery[UserTable])
}

To use Guice DI, you can define UserRepository like this:

@Singleton()
class UserRepository @Inject() (val unicorn: LongUnicornPlayJDBC)
  extends UserRepositoryComponents with UnicornWrapper[Long] {
  import unicorn.driver.api._
  def save(user: User): DBIO[UserId] = UserBaseRepository.save(user)
}

and then inject UserRepository wherever you need it.

Migration to 1.0.x

Version 1.0.x brings Slick 3 new DBIOAction based API to Unicorn. We dropped implicit session parameter from method signatures but we had wrap return types in DBIOAction. We also added implicit executionContext in a few places.

E.g. old BaseIdRepository methods:

  def findById(id: Id)(implicit session: Session): Option[Entity]
  def findExistingById(id: Id)(implicit session: Session): Entity

now become

  def findById(id: Id): DBIO[Option[Entity]]
  def findExistingById(id: Id)(implicit ec: ExecutionContext): DBIO[Entity]

To get to know more about DBIOActions check out Slick 3 documentation.

Migration form 0.5.x to 0.6.x

Version 0.6.x brings possibility for using different type then Long as underlying Id type. The most interesting are UUID and String. This change allow us to start working on typesafe composite keys.

For backward compatibility with 0.5.x we introduced LongUnicornCore and LongUnicornPlay. Before attempting to perform this migration you should known how to migrate your tables definitions to slick-2.1.x. All needed information you could find in awesome migration guide

Core migration

Changes is only on backing your version on unicorn cake. So code like:

object Unicorn extends UnicornCore with HasJdbcDriver {
  val driver = H2Driver
}

now becomes:

object Unicorn extends LongUnicornCore with HasJdbcDriver {
  val driver = H2Driver
}

and this is all your changes.

Play migration

When you use unicorn-play migration is still quite easy, but it will touch all file where unicorn and slick was used.

Imports like those:

import org.virtuslab.unicorn.UnicornPlay._
import org.virtuslab.unicorn.UnicornPlay.driver.simple._

now becomes:

import org.virtuslab.unicorn.LongUnicornPlay._
import org.virtuslab.unicorn.LongUnicornPlay.driver.simple._