99 * jrs.setCommand("SELECT * FROM TITLES WHERE TYPE = ?");
100 * jrs.setURL("jdbc:myDriver:myAttribute");
101 * jrs.setUsername("cervantes");
102 * jrs.setPassword("sancho");
103 * jrs.setString(1, "BIOGRAPHY");
104 * jrs.execute();
105 * </PRE>
106 * The variable <code>jrs</code> now represents an instance of
107 * <code>JdbcRowSetImpl</code> that is a thin wrapper around the
108 * <code>ResultSet</code> object containing all the rows in the
109 * table <code>TITLES</code> where the type of book is biography.
110 * At this point, operations called on <code>jrs</code> will
111 * affect the rows in the result set, which is effectively a JavaBeans
112 * component.
113 * <P>
114 * The implementation of the <code>RowSet</code> method <code>execute</code> in the
115 * <code>JdbcRowSet</code> reference implementation differs from that in the
116 * <code>CachedRowSet</code>™
117 * reference implementation to account for the different
118 * requirements of connected and disconnected <code>RowSet</code> objects.
119 * <p>
120 *
121 * @author Jonathan Bruce
122 */
123
124 public interface JdbcRowSet extends RowSet, Joinable {
125
126 /**
127 * Retrieves a <code>boolean</code> indicating whether rows marked
128 * for deletion appear in the set of current rows. If <code>true</code> is
129 * returned, deleted rows are visible with the current rows. If
130 * <code>false</code> is returned, rows are not visible with the set of
131 * current rows. The default value is <code>false</code>.
132 * <P>
133 * Standard rowset implementations may choose to restrict this behavior
134 * for security considerations or for certain deployment
135 * scenarios. The visibility of deleted rows is implementation-defined
136 * and does not represent standard behavior.
137 * <P>
138 * Note: Allowing deleted rows to remain visible complicates the behavior
139 * of some standard JDBC <code>RowSet</code> implementations methods.
|
99 * jrs.setCommand("SELECT * FROM TITLES WHERE TYPE = ?");
100 * jrs.setURL("jdbc:myDriver:myAttribute");
101 * jrs.setUsername("cervantes");
102 * jrs.setPassword("sancho");
103 * jrs.setString(1, "BIOGRAPHY");
104 * jrs.execute();
105 * </PRE>
106 * The variable <code>jrs</code> now represents an instance of
107 * <code>JdbcRowSetImpl</code> that is a thin wrapper around the
108 * <code>ResultSet</code> object containing all the rows in the
109 * table <code>TITLES</code> where the type of book is biography.
110 * At this point, operations called on <code>jrs</code> will
111 * affect the rows in the result set, which is effectively a JavaBeans
112 * component.
113 * <P>
114 * The implementation of the <code>RowSet</code> method <code>execute</code> in the
115 * <code>JdbcRowSet</code> reference implementation differs from that in the
116 * <code>CachedRowSet</code>™
117 * reference implementation to account for the different
118 * requirements of connected and disconnected <code>RowSet</code> objects.
119 *
120 * @author Jonathan Bruce
121 */
122
123 public interface JdbcRowSet extends RowSet, Joinable {
124
125 /**
126 * Retrieves a <code>boolean</code> indicating whether rows marked
127 * for deletion appear in the set of current rows. If <code>true</code> is
128 * returned, deleted rows are visible with the current rows. If
129 * <code>false</code> is returned, rows are not visible with the set of
130 * current rows. The default value is <code>false</code>.
131 * <P>
132 * Standard rowset implementations may choose to restrict this behavior
133 * for security considerations or for certain deployment
134 * scenarios. The visibility of deleted rows is implementation-defined
135 * and does not represent standard behavior.
136 * <P>
137 * Note: Allowing deleted rows to remain visible complicates the behavior
138 * of some standard JDBC <code>RowSet</code> implementations methods.
|