Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8234839
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T18:37:11+00:00 2026-06-07T18:37:11+00:00

I currently am working on a project that does a lot of work with

  • 0

I currently am working on a project that does a lot of work with Database.

One core idiom that I have reused many, many times in my code is the following.

My question is, is there a better way to handle the exceptions at each step of the getTransformedResults method? Is this a proper way of handling the SQLExceptions, or is there a better, more concise way of doing this?

Thanks for your input!

public ResultType handleResultSet(ResultSet rs);

public ResultType getTransformedResults(String query) throws SQLException {
  ResultType resultObj = new ResultType();

  Connection connection = null;
  try { 
    connection = dataSource.getConnection();
  } catch (SQLException sqle) {
    // cleanup 
    throw sqle;
  }

  Statement stmt = null;
  try { 
    stmt = connection.createStatement();
  } catch (SQLException sqle) {
    try { connection.close() } catch (SQLException dontCare) {}
    // cleanup
    throw sqle;
  }

  ResultSet rs = null;
  try { 
    ResultSet rs = stmtm.executeQuery(query);
    resultObj = handleResultSet(rs);
  } catch (SQLException sqle) {
    // cleanup
    throw sqle;
  } finally {
    if (rs != null) try { rs.close() } catch (SQLException dontCare) {}
    try { stmt.close() } catch (SQLException dontCare) {}
    try { connection.close() } catch (SQLException dontCare) {}
  }

  return resultObj;
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T18:37:13+00:00Added an answer on June 7, 2026 at 6:37 pm

    You may be interested in using Apache Commons DbUtils which is aimed exactly at such purposes.

    It has some drawbacks when trying to use more sophisticated JDBC but for regular usage it should be more than enough.

    Besides that, your code contains too much try/catch blocks and can be simplified to something like the following:

    public interface ResultSetHandler<ResultType> {
         ResultType handleResultSet(ResultSet rs);
    }
    
    public <ResultType> ResultType getTransformedResults(String query, ResultSetHandler<ResultType> rsh) throws SQLException {      
      Connection connection = null;
      Statement stmt = null;
    
      try { 
        connection = dataSource.getConnection();
        stmt = connection.createStatement();
        ResultSet rs = stmtm.executeQuery(query);
        return rsh.handleResultSet(rs);
      } catch (SQLException sqle) {
        // cleanup 
        throw sqle;
      } finally {
        if(stmt != null) {
          statement.close(); // closes also resultSet
          connection.close();
        }
      }
    }
    

    Though Apache Commons DbUtils library does exactly the same under the hood.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm currently working on a project that does a lot of HTTP requests for
I am currently working on a project that involves many subprojects that all have
Currently I'm working on the project that does processing files from source directory in
I am currently working on a project that is looking at having a database
Currently the project I'm working with does not have completely fixed models (due to
I have an idea for a project that I am currently working on, I
I'm currently working on a project that's based on Android. Without getting into many
I'm currently working on a project that involves a lot of text file reading.
I am currently working on a project that will work on a membership system.
I am currently working on a project that requires me to display PDF documents

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.