Hmm, still not quite understanding what you want to do. If you don't know the type of the bind value, you should just use setObject(). H2 has a lot of internal convert logic to handle converting it to the correct type.
On Tue, Jan 3, 2012 at 15:31, Lukas Eder <[email protected]> wrote: >> That way that H2 works, that's a valid error because the bytestream for the> >> string "10" is not a valid serialised object. > But then, the problem is in CAST(? AS OTHER), I guess? If "10" > cannotbe properly serialised, it might be better when the error occurs > atserialisation time, not at deserialisation time... Or maybe CAST > isnot the right function to convert "10" into the data type "OTHER"? >> Why would you want to cast to OTHER? > I'm playing around with various options of handling H2's strongtyping. > Sometimes, the type of a bind value is not known in Java code.Some > more weakly typed databases can handle that, but with H2 (as wellas > HSQLDB, Derby, DB2) casting is necessary. In my case, OTHER isprobably > a bad choice, though. -- 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.
