Hi, > If I understand that little snippet of code correctly, does that mean > that when using an updatable result which involves a serialized java > object, like in my test case, you will take the performance hit of > serialization/deserialization on the object, even if you are not > updating the object itself?
Yes. It's not optimal, I agree. But I don't think it's not a big problem for performance. If it turns out it is a problem in practice, it can be improved. > In general, i would be curious as to you thoughts on using > UpdatableResultSet. Does it provide any real performance benefit - or > is a straightfoward implementation which is mostly there in the > interest of conforming to JDBC spec. You are right, there is no performance benefit at the moment. The main reason why I implemented this feature is: compatibility, standard compliance, and ease-of-use. Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
