Description
For simple ResultSet usage like:
ResultSet rs = ps.executeQuery();
while (rs.next())
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?
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-3004 Get rid of the finalizer in EmbedResultSet
- Closed
- is related to
-
DERBY-1879 Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
- Closed
- relates to
-
DERBY-2139 executing getXXX() for a column checks the column position is in range three times, reduce to one.
- Open
-
DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.
- Closed
-
DERBY-1957 Factor out run-time statistics information from language ResultSet classes
- Closed