Thanks, I understand the issue. But keep in mind, that the main issue in serialization and deserialization of jOOQ Records is the aforementioned use of toString as a last resort. toString will yield in almost any case to serialized (json) data which is not deserializable anymore, as user types usually don't have a string based constructor.
So I would suggest to go with sql datatypes <T>. Here the value of the user type <U> needs to be converted back to <T> during format json. Then serialize the known sql datatype to json. In this case json would have BIGINT with the Long value. Deserialization goes in reverse order. -- 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
