code: public void close() throws SQLException {
  
          if (navigator == null) {
              return;
          }
          navigator.close();
  
          navigator = null;
  
          if (autoClose && statement != null) {
              statement.close();
          }
      }
docs: <!-- start generic documentation -->
  Releases this <code>ResultSet</code> object's database and
  JDBC resources immediately instead of waiting for
  this to happen when it is automatically closed.
  
  <P>(JDBC4 clarification:)
  The closing of a <code>ResultSet</code> object does <strong>not</strong> close the <code>Blob</code>,
  <code>Clob</code> or <code>NClob</code> objects created by the <code>ResultSet</code>. <code>Blob</code>,
  <code>Clob</code> or <code>NClob</code> objects remain valid for at least the duration of the
  transaction in which they are created, unless their <code>free</code> method is invoked.
  <p>
  (JDBC4 clarification:)
  When a <code>ResultSet</code> is closed, any <code>ResultSetMetaData</code>
  instances that were created by calling the  <code>getMetaData</code>
  method remain accessible.
  
  <P><B>Note:</B> A <code>ResultSet</code> object
  is automatically closed by the
  <code>Statement</code> object that generated it when
  that <code>Statement</code> object is closed,
  re-executed, or is used to retrieve the next result from a
  sequence of multiple results.
  (JDBC4 deleted:) [A <code>ResultSet</code> object is also automatically
  closed when it is garbage collected.]
  <p>
  Calling the method <code>close</code> on a <code>ResultSet</code>
  object that is already closed is a no-op.
  <P>
  <p>
  <!-- end generic documentation -->
  
  @exception SQLException if a database access error occurs