Question 1

How to set up Skunk with a basic Scala application?

Accepted Answer

Start by adding Skunk dependencies to your build.sbt, then create a Session resource using Cats Effect's IO. You'll need to configure a PostgreSQL connection and manage resources functionally, as shown in the microsite examples.

Question 2

Skunk vs Doobie: which one should I use for PostgreSQL?

Accepted Answer

Skunk is PostgreSQL-specific with deeper optimizations and type-safety, while Doobie supports multiple databases and has a larger ecosystem. Choose Skunk for pure FP and Postgres focus; Doobie for flexibility across databases.

Question 3

Does Skunk support JSONB and other PostgreSQL advanced types?

Accepted Answer

Yes, Skunk natively supports PostgreSQL-specific data types like JSONB, arrays, and enums through its type-safe API, leveraging the binary protocol for efficient serialization and deserialization.

Question 4

How to handle errors and retries with Skunk?

Accepted Answer

Errors are managed functionally using Cats Effect's error-handling mechanisms, such as IO monads and resources. You can implement retries with libraries like cats-retry, but Skunk doesn't provide built-in retry logic.

Question 5

Can I use Skunk with non-Cats Effect frameworks like ZIO?

Accepted Answer

Skunk is tightly coupled with Cats Effect, so using it with ZIO requires interoperability layers like zio-interop-cats, which can add complexity and might not support all features seamlessly.

Question 6

What's the performance overhead of Skunk compared to plain JDBC?

Accepted Answer

Skunk adds some overhead due to its functional abstractions and type-safety, but it optimizes with PostgreSQL's binary protocol to mitigate this. For simple queries, plain JDBC might be faster, but Skunk excels in safety and scalability.

skunk

What is skunk?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions