Haha, good! But what about the field columnLabelMap? From what I can that is re-calcalculated in every new instance of JdbcResultSet. Can't that be cached as well?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Noel Grandin Sent: den 23 april 2012 22:45 To: [email protected] Subject: Re: Potential performance improvement Good idea. We already do that :-) On Mon, Apr 23, 2012 at 22:21, Carl Hasselskog <[email protected]> wrote: > That's a cool idea! I also had another (which is not mutually exclusive to > yours). Perhaps one can cache the column-mapping in JdbcPreparedStatement and > re-use it for every execution of the same query. I don't know if there's any > corner case where JdbcPreparedStatement might have different column-mappings > in different executions but perhaps one can make it an optional feature? > -- 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. -- 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.
