> This is known limitation. Currently H2 does not know how to convert string > to your object type other then to parse hexadecimal data.
This is not the problem. The real problem is that Strings are trying to be transformed to the Java object rather than transforming the Java object to String. When the object is not serialized (cf newly introduced system property), the object has a String representation which should be used when comparing to strings. My original implementation, which was not performant because it was deserializing for every operation (and for which I was planning to do what you essentially did), at least got this right (in my opinion). I believe that transforming a String as if it were the bytes of a serialized object is nonsense, especially in the case where we don't serialize. Hope this helps, -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.
