I've accidentally built a compilation benchmark harness for Scala 2 and 3 which can measure the cost (in compilation time) for having a codebase full of implicits which need to be resolved. Read on to see the results!

Thanks to the efforts of Jules Ivanic in PR #57, Typo now supports using zio-jdbc as a database library.

Never heard of Typo?​

You can check out the introduction. Essentially it's a code generator for database access code, which makes PostgreSQL integration type-safe and wonderful to use.

Maturity​

Note that zio-jdbc is a bit less mature than doobie and anorm, so it's a bit more likely to be some rough edges. In particular, it handles nullable values imperfectly. We fixed a bunch of issues while working on this PR, so it should be pretty close.

Implemented missing features in zio-jdbc​

zio-jdbc does not support postgres arrays, and it does not support the COPY API for streaming inserts.

Typo outputs code which implements both of these features.

This can likely be upstreamed as a postgres integration module in zio-jdbc at some point.