Hi Thomas, > The current implementation of this feature is geared towards high > performance, which means trying to avoid serialization (at least for > in-memory databases), trying to avoid calling toString, and rather > calling the classes compareTo, hashCode, and equals methods.
There is no performance problem to consider that comparing String and Non-Serialized Java Object should use String as the comparison type instead of the object. This comparison would then obviously use the toString method of the Non-Serialized Java Object for the comparison with the String. Cheers, -Christopher -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
