Zoltán Farkas

Here is a complete test code based on the previous message of @dvail Tested module: `com.fasterxml.jackson.module:jackson-module-kotlin:2.13.4` ```kotlin import com.fasterxml.jackson.annotation.JsonProperty import com.fasterxml.jackson.module.kotlin.jacksonObjectMapper import com.fasterxml.jackson.module.kotlin.readValue import org.junit.jupiter.api.Assertions import org.junit.jupiter.api.Test @JvmInline value class...

## Here is the API of PGJDBC `Connection` of PGJDBC provides `LargeObjectManager` via `connection.unwrap(PGConnection.class).getLargeObjectAPI()` Methods of `LargeObjectManager`: - `LargeObject open(long oid, int mode)` opens an existing large object, based on...

I reconsidered my request. `LargeObject` is memory efficient because the client code uses the same byte array in a loop. With reactive stream data is immutable so we can consume...

> An extra plus for this implementation would be support for kotlin's `value class`es which I think Jackson can't support... Oh yes! This is my primary reason for preferring kotlinx...