-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
8, 9
-
generic
-
generic
A DESCRIPTION OF THE REQUEST :
For a while now I've been annoyed when working with CachedRowSets in Java. Simple things such as
return new CachedRowSetImpl().populate(statement.executeQuery());
aren't possible, because the method populate is a void and doesn't return anything. If this specific method would return a CachedRowSet, this would be possible
JUSTIFICATION :
It just makes our lives easier and saves us some time and code.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
CachedRowSetImpl#populate(ResultSet) should return a CachedRowSet
ACTUAL -
CachedRowSetImpl#populate(ResultSet) should return a CachedRowSet
---------- BEGIN SOURCE ----------
CachedRowSet cachedResult = new CachedRowSetImpl().populate(statement.executeQuery());
return new CachedRowSetImpl().populate(statement.executeQuery());
---------- END SOURCE ----------
For a while now I've been annoyed when working with CachedRowSets in Java. Simple things such as
return new CachedRowSetImpl().populate(statement.executeQuery());
aren't possible, because the method populate is a void and doesn't return anything. If this specific method would return a CachedRowSet, this would be possible
JUSTIFICATION :
It just makes our lives easier and saves us some time and code.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
CachedRowSetImpl#populate(ResultSet) should return a CachedRowSet
ACTUAL -
CachedRowSetImpl#populate(ResultSet) should return a CachedRowSet
---------- BEGIN SOURCE ----------
CachedRowSet cachedResult = new CachedRowSetImpl().populate(statement.executeQuery());
return new CachedRowSetImpl().populate(statement.executeQuery());
---------- END SOURCE ----------