OPENJPA-1550 Fix comment

git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@921177 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Donald Woods 2010-03-09 22:34:06 +00:00
parent 695bd9c4bf
commit f82184314e
1 changed files with 3 additions and 3 deletions

View File

@ -194,8 +194,8 @@ public class BatchingPreparedStatementManagerImpl extends
//When we do a 'getNextException', the 'next exception' doesn't contain the same message as se.
//That is, 'next exception' contains a subset msg which is contained in se. For legacy, should
//we continute to use 'sqex' in the 'old path' and use 'se' in the next path/code?????
// SQLException sqex = se.getNextException();
// if (sqex == null)
//SQLException sqex = se.getNextException();
//if (sqex == null)
// sqex = se;
SQLException sqex = se;