All Implemented Interfaces:
ResultSetobject that makes it possible to use the result set as a JavaBeansTM component. Thus, a
JdbcRowSetobject can be one of the Beans that a tool makes available for composing an application. Because a
JdbcRowSetis a connected rowset, that is, it continually maintains its connection to a database using a JDBC technology-enabled driver, it also effectively makes the driver a JavaBeans component.
Because it is always connected to its database, an instance of
can simply take calls invoked on it and in turn call them on its
ResultSet object. As a consequence, a result set can, for
example, be a component in a Swing application.
Another advantage of a
JdbcRowSet object is that it can be
used to make a
ResultSet object scrollable and updatable. All
RowSet objects are by default scrollable and updatable. If
the driver and database being used do not support scrolling and/or updating
of result sets, an application can populate a
with the data of a
ResultSet object and then operate on the
JdbcRowSet object as if it were the
JdbcRowSetImpl, provides an implementation of the default constructor. A new instance is initialized with default values, which can be set with new values as needed. A new instance is not really functional until its
executemethod is called. In general, this method does the following:
PreparedStatementobject and sets any of its placeholder parameters
executemethod is successful, it will set the appropriate private
JdbcRowSetfields with the following:
Connectionobject -- the connection between the rowset and the database
PreparedStatementobject -- the query that produces the result set
ResultSetobject -- the result set that the rowset's command produced and that is being made, in effect, a JavaBeans component
executemethod has not executed successfully, no methods other than
closemay be called on the rowset. All other public methods will throw an exception.
Before calling the
execute method, however, the command
and properties needed for establishing a connection must be set.
The following code fragment creates a
sets the command and connection properties, sets the placeholder parameter,
and then invokes the method
JdbcRowSetImpl jrs = new JdbcRowSetImpl(); jrs.setCommand("SELECT * FROM TITLES WHERE TYPE = ?"); jrs.setURL("jdbc:myDriver:myAttribute"); jrs.setUsername("cervantes"); jrs.setPassword("sancho"); jrs.setString(1, "BIOGRAPHY"); jrs.execute();The variable
jrsnow represents an instance of
JdbcRowSetImplthat is a thin wrapper around the
ResultSetobject containing all the rows in the table
TITLESwhere the type of book is biography. At this point, operations called on
jrswill affect the rows in the result set, which is effectively a JavaBeans component.
The implementation of the
execute in the
JdbcRowSet reference implementation differs from that in the
reference implementation to account for the different
requirements of connected and disconnected
|Method from javax.sql.rowset.JdbcRowSet Summary:|
|commit, getAutoCommit, getRowSetWarnings, getShowDeleted, rollback, rollback, setAutoCommit, setShowDeleted|
|Method from javax.sql.rowset.JdbcRowSet Detail:|
public void commit() throws SQLException
Makes all changes made since the previous commit/rollback permanent and releases any database locks currently held by this Connection object. This method should be used only when auto-commit mode has been disabled.
public boolean getAutoCommit() throws SQLException
Sets this connection's auto-commit mode to the given state. If a connection is in auto-commit mode, then all its SQL statements will be executed and committed as individual transactions. Otherwise, its SQL statements are grouped into transactions that are terminated by a call to either the method commit or the method rollback. By default, new connections are in auto-commit mode.
public RowSetWarning getRowSetWarnings() throws SQLException
Because it is always connected to its data source, a
public boolean getShowDeleted() throws SQLException
Standard rowset implementations may choose to restrict this behavior for security considerations or for certain deployment scenarios. The visibility of deleted rows is implementation-defined and does not represent standard behavior.
Note: Allowing deleted rows to remain visible complicates the behavior
of some standard JDBC
public void rollback() throws SQLException
public void rollback(Savepoint s) throws SQLException
public void setAutoCommit(boolean autoCommit) throws SQLException
Sets the current auto-commit mode for this
public void setShowDeleted(boolean b) throws SQLException
Standard rowset implementations may choose to restrict this behavior for security considerations or for certain deployment scenarios. This is left as implementation-defined and does not represent standard behavior.