Question 1

How do I set up Slonik with Zod for validating query results?

Accepted Answer

You need to add a result parser interceptor, like the example in the README, which uses Zod to validate rows in `transformRow`. Then, use `sql.type` with a Zod schema in your queries to enforce runtime checks and type safety.

Question 2

Slonik vs pg-promise: which one should I choose?

Accepted Answer

Slonik is better for teams prioritizing SQL injection safety via tagged templates and runtime validation, while pg-promise offers more flexibility with dynamic SQL and a mature ecosystem. Slonik's interceptors provide middleware extensibility, but pg-promise has broader community support.

Question 3

Can I use Slonik with Express.js for a web API?

Accepted Answer

Yes, Slonik integrates well with Express.js; the README references an article on this. You typically create a connection pool and use it in route handlers, ensuring safe query execution with the `sql` tag for parameterized queries.

Question 4

How does Slonik handle connection pooling to prevent leaks?

Accepted Answer

Slonik uses `pool.connect()` to scope connections to promise routines, automatically releasing them after execution. This prevents leaks by ensuring connections are always cleaned up, even if errors occur, as explained in the connection handling section.

Question 5

Is Slonik good for small projects or beginners?

Accepted Answer

Not ideal; its strict patterns and configuration overhead make it better suited for larger teams needing robust safety. Beginners might find simpler clients like `node-postgres` easier to start with due to Slonik's learning curve.

Question 6

What's the performance impact of Slonik's runtime validation?

Accepted Answer

The README notes a performance penalty, e.g., sub 0.1ms per row, scaling up with result size. For most applications, this is negligible compared to network latency, but it can add up in data-intensive scenarios.

Question 7

How to log queries and debug issues in Slonik?

Accepted Answer

Slonik uses Roarr for structured logging; enable it in configuration to get detailed logs with stack traces and query values. You can also add custom interceptors for query logging or benchmarking, as shown in the community interceptors list.

slonik

What is slonik?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions