Hi Jake, > Thanks for the reply, Lukas. I found a workaround by simply registering a > custom data type handler to the Postgres JDBC Connection. Then just cast the > record field to the custom data type object class. Seems to work like a > charm.
Great! If you get this working more stably, I'd be curious to see some sample code. This might be an interesting thing to document in the "advanced" section of the jOOQ manual, as other users might profit from that information as well. > It doesn't look like Postgres has direct support for this type yet, > but I believe it's on their radar. Unfortunately, the Postgres JDBC driver lacks a lot of implementation. For instance, regular user defined types are not really supported either, unless you're ready to parse their string representation manually... > Great work, by the way, on this API. It > took a little convincing on my part to get our team off of the Hibernate > bandwagon, but everyone is really starting to take a liking to how well > thought-out the implementation is. Kudos for bringing some sanity back to > Java! Thank you! I'm sure when you start using stored functions and Postgres' advanced features, you'll soon get to the limits of Hibernate. Feel free to publish a success story on your blog, if you have time. Also, if you find something is missing, feel free to create another feature request. Cheers Lukas
