Joachim, > On the performance side, comparing unequal strings (the normal case) cannot > declare inequality if == does not hold because one of the strings might be > uninterned. You'll have an advantages only when comparing strings that turn > out to be equal. This means that you'll probably have to halve the effect.
On the other hand, String.equals() is more expensive for equal strings. As UUID are "highly unequal" thanks to the time_low field being first in the string, interning might indeed accelerate things significantly in benchmarks -- 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.
