java.sql.ResultSet

Table 1. JDBC 2.0 ResultSet Methods Supported
Returns	Signature	Implementation Notes
void	afterLast()
void	beforeFirst()
void	beforeFirst()
void	deleteRow()	After the row is updated, the ResultSet object will be positioned before the next row. Before issuing any methods other than close on the ResultSet object, the program will need to reposition the ResultSet object by using the next() method.
boolean	first()
Blob	getBlob(int columnIndex)	See java.sql.Blob and java.sql.Clob
Blob	getBlob(String column-Name)
Clob	getClob(int columnIndex)
Clob	getClob(String column-Name)
int	getConcurrency()	If the Statement object has CONCUR_READ_ONLY concurrency, then this method will return ResultSet.CONCUR_READ_ONLY. But if the Statement object has CONCUR_UPDATABLE concurrency, then the return value will depend on whether the underlying language ResultSet is updatable or not. If the language ResultSet is updatable, then getConcurrency() will return ResultSet.CONCUR_UPDATABLE. If the language ResultSet is not updatable, then getConcurrency() will return ResultSet.CONCUR_READ_ONLY.
int	getFetchDirection()
int	getFetchSize()	Always returns 1.
int	getRow()
boolean	isAfterLast()
boolean	isBeforeFirst
boolean	isFirst()
boolean	isLast()
boolean	last()
boolean	previous()
boolean	relative(int rows)
void	setFetchDirection(int direction)
void	setFetchSize(int rows)	A fetch size of 1 is the only size supported.
void	updateRow()	After the row is updated, the ResultSet object will be positioned before the next row. Before issuing any methods other than close on the ResultSet object, the program will need to reposition the ResultSet object by using the next() method.

Note: When working with scrolling insensitive ResultSets when auto-commit mode is turned on, the only positioning method that can close the ResultSet automatically is the next() method. When auto-commit mode is on, this method automatically closes the ResultSet if it is called and there are no more rows. afterLast() does not close the ResultSet, for example.

JDBC is not required to have auto-commit off when using updatable ResultSets.

At this moment, Derby does not support the insertRow() method for updatable ResultSets.