e("\"", "")));
> }
> ,
> m -> m.entrySet()
> .stream()
> .map(e -> "\"" + e.getKey() + "\"=>\"" + e.getValue() +
> "\",")
>
My question is similar (and perhaps is covered already) but goes in a
slightly different direction.
I really like the JOOQ record mapper implementation for fetching
"auto-magically" straight into custom POJOs - we tend to use this a bit
when our domain classes don't nicely reflect what can be
Hi Lukas,
A contrived table and UDT setup to demonstrate the issue would be as
follows:
CREATE TYPE message AS (
definition TEXT,
parameters HSTORE
);
CREATE TABLE person (
id BIGINT NOT NULL,
messages message[],
PRIMARY KEY (id)
);
Here is the binding
Hi there!
Perhaps an unusual case but one I ran into today:
If I have a Postgres UDT ('MyUdt') that contains a field mapped with a
custom JOOQ binding (like a hstore or json field as mentioned here:
http://www.jooq.org/doc/3.8/manual/code-generation/custom-data-type-bindings/)
and that UDT is
