Dear group, Part of jOOQ's success is its incredible amount of convenience methods that help reduce the boiler plate code at your side. We do this with massive overloading of API, for instance, when you work with fetch(), you may have noticed how many different types of fetch() there are in jOOQ.
Just now, I have added yet another convenience method. A Converter constructor: https://github.com/jOOQ/jOOQ/issues/5398 It looks like this: static <T, U> Converter<T, U> of( Class<T> fromType, Class<U> toType, Function<? super T, ? extends U> from, Function<? super U, ? extends T> to ) { ... } And also: static <T, U> Converter<T, U> ofNullable( Class<T> fromType, Class<U> toType, Function<? super T, ? extends U> from, Function<? super U, ? extends T> to ) { return of( fromType, toType, t -> t == null ? null : from.apply(t), u -> u == null ? null : to.apply(u) ); } The above allows for creating simple ad-hoc, one-liner converters, such as: Converter<String, Integer> converter = Converter.ofNullable(String.class, Integer.class, Integer::parseInt, Object::toString); What's your biggest "itch" in the jOOQ API, which jOOQ could "scratch", or rather, make go away by adding new convenience API? All ideas welcome! Lukas -- 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.
