Hello Adam, Hmm, I'm not sure if I understand your use case, where String internalisation could significantly improve jOOQ's performance. What String values did you want to intern? The key names? Or the key values if they're strings? Have you done any measurements / benchmarks?
Cheers Lukas 2013/2/6 Adam <[email protected]>: > Hi Lukas, > > I was wondering if it would be possible to internalize string keys (calling > intern() method) for both primary and foreign keys (as defined in the Keys > class) when these are selected from the database during the record > construction. > > String internalization will eliminate duplicates and improve performance > during the key comparison (executing ‘==’ instead of a more expensive per > char comparison) as surrogate primary keys are often used in > equals()/hashCode(). This could be either a default behaviour or there could > be an option for the code generator (since there is performance hit for the > ‘intern()’ call). > > Regards, > > Adam > > > -- > 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/groups/opt_out. > > -- 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/groups/opt_out.
