zio.cassandra.session.cql.codec

Low-level alternative for com.datastax.oss.driver.api.core.type.codec.TypeCodec that is meant ot be resolved at a compile-time.
Its main purpose is to provide a deserializer for a single column value (regardless of if it's a primitive type or an UDT).

Low-level alternative for com.datastax.oss.driver.api.core.type.codec.TypeCodec that is meant ot be resolved at a compile-time.
Its main purpose is to provide a serializer for a single column value (regardless of if it's a primitive type or an UDT).

The main typeclass for decoding Cassandra values, the only one that matters.
zio.cassandra.session.cql.codec.CellReads and zio.cassandra.session.cql.codec.UdtReads are mostly an implementation details. As long as you can provide and instance of zio.cassandra.session.cql.codec.Reads for your class (regardless of how you've created it), everything should work just fine.

Deserializer created specifically for UDT values.
Note that unlike zio.cassandra.session.cql.codec.Reads, this reader can be (is) recursive, so each instance of zio.cassandra.session.cql.codec.UdtReads can be seen as an instance of zio.cassandra.session.cql.codec.CellReads, while at the same time it might need zio.cassandra.session.cql.codec.CellReads instances to work.

Serializer created specifically for UDT values.
Note that this reader can be (is) recursive, so each instance of zio.cassandra.session.cql.codec.UdtWrites can be seen as an instance of zio.cassandra.session.cql.codec.CellWrites, while at the same time it might need zio.cassandra.session.cql.codec.CellWrites instances to work.

The reason why it needs structure: UdtValue param is because we cannot create an UdtValue out of thin air, we can only fill it with values. The only one who can properly create an UdtValue is java driver, so it's up to a caller to ask the driver to create a dummy UdtValue, which we'll use.