title: Apache DBUtils - Why need resultsethandler for Insert?
body: <p>I run an insert statement using Apache DBUtils. However, I am not sure why I have to include ResultSetHandler for this case:</p>
  
  <pre><code>String theQuery = QueryGenerator.insertintoStats();
          ResultSetHandler&lt;Object&gt; dummyHandler = new ResultSetHandler&lt;Object&gt;() {
              @Override
              public Object handle(ResultSet rs) throws SQLException
              {
                  return null;
              }
          };
          try
          {
              queryRunner.insert(connection, theQuery, dummyHandler, Constants.UUIDSTR.toString(), name, prevbackupTime,
                      curbackupTime, updStartTime, delStartTime, bkupType.toString(), rowCount);
          }
          catch (SQLException e)
          {
              LOGGER.info(theQuery.toString());
              LOGGER.error("Caught exception!", e);
          }
  </code></pre>
  
  <p>Similar's the case for <code>insertbatch</code> which does use ResultSetHandler. I have resorted to use <code>batch</code> call for batch queries. Can anyone explain why we would be needing resultset handler for <code>insert</code>?</p>