On Wed, Oct 24, 2018 at 7:27 PM Marshall Pierce <[email protected]> wrote:
> Gotcha. Not surprising that there are 470 overloads I don't know about > yet in jOOQ that make it complex to automatically cache, but is it at > least feasible to opt in to caching so that a consumer could use it when > they're always looking up the same way (as I am)? Perhaps a > .cachedSomethingOrOther() that returns another Result -- that transient > object would be convenient to GC if it's only used in a loop, for instance. > But how would that work? By the time this caching mechanism has identified the cache key (e.g. composed of all the fields of the source record type and all the fields of the target record type), the actual mapping would have executed many times... -- 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.
