[ https://issues.apache.org/jira/browse/DERBY-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-1876: -------------------------------------- Derby Info: (was: [Patch Available]) Committed timeout_colcount.diff with revision 522445. > Investigate overhead of JDBC layer and compiled activation code for simple > embedded read-only, forward ResultSets > ----------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1876 > URL: https://issues.apache.org/jira/browse/DERBY-1876 > Project: Derby > Issue Type: Improvement > Components: JDBC, Performance > Reporter: Daniel John Debrunner > Priority: Minor > Attachments: derby1862.java, derby1876.java, timeout_colcount.diff > > > For simple ResultSet usage like: > ResultSet rs = ps.executeQuery(); > while (rs.next()) { > rs.getInt(1); > rs.getInt(2); > rs.getInt(3); > } > rs.close(); > it would be interesting to see how much overhead could be removed with simple > changes, or possibly removed if there was a simple ResultSet implementation > for forward only, read-only ResultSet, and the more complete implementation > for all other ResultSet types such as updateable and/or scrollable. Has > introducing updateable ResultSets, for example, degraded the performance of > read-only ResultSets? Could code be changed so that a typical read-only > Resultset is not affected by the code required for richer ResultSets? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.