doobie-quill
doobie
doobie-quill | doobie | |
---|---|---|
2 | 12 | |
33 | 2,122 | |
- | - | |
7.1 | 8.8 | |
almost 2 years ago | 7 days ago | |
Scala | Scala | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
doobie-quill
doobie
-
Grasping the concepts and getting them down to earth
Most important/known: * https://http4s.org/ - an HTTP client/server * https://github.com/typelevel/fs2 - streaming * https://github.com/tpolecat/doobie - JDBC
-
doobie map to PostGIS Point
So you need to use PGgeography scala type and import another set of implicits: https://github.com/tpolecat/doobie/blob/main/modules/postgres/src/main/scala/doobie/postgres/pgisgeographyinstances.scala
-
mod team resignation by BurntSushi · Pull Request #671 · rust-lang/team
Developer removing a library integration due to above politics
- Remove Quill Integration
-
It's unsafe to depend on Typelevel Libraries
Doobie removes Quill integration in order to make some sort of political protest. The Quill developers are harassed on Twitter.
- Why is tpolecat against ZIO?
- Removes integration with Quill, which is now part of the ZIO organization, which I will not support
-
Zio / Zionomicon : is it worth it ?
The libraries doobie and skunk are more closely associated with cats. They both use cats-effect and fs2 for implementing database connectiona and input-output operations. The doobie library is a wrapper on JDBC, and as such is compatible with many DBMS, such as MySQL, PostgreSQL, H2, Oracle... Whereas skunk is specific to PostgreSQL, and is based on using the server protocol of that database.
-
Hiding Doobie's ConnectionIO implementation detail
You may find this issue helpful. tl;dr you can easily make a Transactor with the void Strategy that just ignores the null Connection. But I’m with Rob: at that point, you’re not actually testing anything.
What are some alternatives?
cats-effect - The pure asynchronous runtime for Scala
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
skunk - A data access library for Scala + Postgres.
Quill - Compile-time Language Integrated Queries for Scala
scala-pet-store - An implementation of the java pet store using FP techniques in scala
cancel-culture - Tools for fighting abuse on Twitter
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
Monix - Asynchronous, Reactive Programming for Scala and Scala.js.
Anorm - The Anorm database library
toolkit - A Scala 3, lightweight and functional non-intrusive library to build typed and declarative Scala application with managed resources and dependencies
Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support