2018-03-18 22:04 GMT+01:00 The bear in Boulder <[email protected]>:
> > > On Friday, August 18, 2017 at 7:31:15 AM UTC-6, Lukas Eder wrote: >> >> >> >> 2017-08-17 21:21 GMT+02:00 <[email protected]>: >> >>> I want to bind my composite type to my own Java object and not to the >>> UDT object generated by Jooq. >>> >> >> I wouldn't do that if I were you. We've fixed tons of bugs over the last >> releases to get this to work with all sorts of potentially nested UDTs and >> arrays and what not. The PostgreSQL JDBC driver is very incomplete as far >> as binding PostgreSQL's advanced data types are concerned. Ultimately, it >> just boils down to parsing / serialising things to strings. >> >> Having said so, you can easily apply a Converter (rather than a Binding) >> to automatically map the generated jOOQ UDTRecord to your custom type. >> Implementing a Converter is also much simpler than implementing a Binding >> >> I hope this helps >> Lukas >> > > What do you need from the PostgreSQL JDBC driver? I've only looked at some > of the Kerberos auth stuff but there's a (remote) possibility that I could > help. > The PostgreSQL JDBC driver doesn't help at all, its support for PostgreSQL's data types is non-existent. It just transmits a string-serialized version of all sorts of types and wraps that in PGobject. Essentially, jOOQ includes a string serializer / deserializer for this PostgreSQL object notation. I'm not sure in what context you're asking this question though. Perhaps, you could create a new discussion - in case it's not really related to this previous one... -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
