From c3710283453ee15e7891c40eba6cddb4d0b8216e Mon Sep 17 00:00:00 2001 From: Will Sargent Date: Thu, 13 Feb 2020 20:35:29 -0800 Subject: [PATCH] Update docs/manual/working/scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md Co-Authored-By: Marcos Pereira --- .../scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md b/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md index 333796b4..8b4d54f3 100644 --- a/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md +++ b/docs/manual/working/scalaGuide/main/sql/slick/PlaySlickAdvancedTopics.md @@ -8,7 +8,7 @@ In Play Slick we have decided to let Slick be in control of creating and managin Also, note that as stated in the [Slick documentation](http://scala-slick.org/doc/3.3.2/database.html#connection-pools), a reasonable default for the connection pool size is calculated from the thread pool size. In fact, you should only need to tune `numThreads` and `queueSize` in most cases, for each of your database configuration. -Finally, it's worth mentioning that while Slick allows using a different connection pool than [HikariCP](https://github.com/brettwooldridge/HikariCP) (though, Slick currently only offers built-in support for HikariCP, and requires you to provide an implementation of [JdbcDataSourceFactory](http://scala-slick.org/doc/3.3.2/api/index.html#slick.jdbc.JdbcDataSourceFactory) if you want to use a different connection pool), Play Slick currently doesn't allow using a different connection pool than HikariCP. +Finally, it's worth mentioning that while Slick allows using a different connection pool than [HikariCP](https://github.com/brettwooldridge/HikariCP) (though, Slick currently only offers built-in support for HikariCP, and requires you to provide an implementation of [JdbcDataSourceFactory](https://scala-slick.org/doc/3.3.2/api/index.html#slick.jdbc.JdbcDataSourceFactory) if you want to use a different connection pool), Play Slick currently doesn't allow using a different connection pool than HikariCP. > **Note**: Changing the value of `play.db.pool` won't affect what connection pool Slick is using. Furthermore, be aware that any configuration under `play.db` is not considered by Play Slick.