title: Should I Catch EmptyResultDataAccessException?
body: <p>I have a SQL statement that I expect will return one row, because I am passing the primary key.  So my choices are to </p>
  
  <ol>
  <li>Wrap the <strong>queryForObject</strong> in a try/catch, catching EmptyResultDataAccessException, and returning null</li>
  <li>Change the call to <strong>queryForList</strong>, and unwrap the List and (hopefully) return the 1st element, or null.</li>
  </ol>
  
  <p>I read somewhere the cathing an EmptyResultDataAccessException, since it extends runtime exception, is a bad practice.</p>
  
  <p>But I can't see anything wrong with it.</p>
  
  <p>I would be interested in hearing opinions</p>