Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E297FF85 for ; Mon, 13 May 2013 20:55:58 +0000 (UTC) Received: (qmail 56614 invoked by uid 500); 13 May 2013 20:49:18 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 56483 invoked by uid 500); 13 May 2013 20:49:18 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 56472 invoked by uid 99); 13 May 2013 20:49:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 20:49:18 +0000 Date: Mon, 13 May 2013 20:49:18 +0000 (UTC) From: "Sebb (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DBUTILS-109) AbstractExecutor.currentPosition should be an int MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DBUTILS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved DBUTILS-109. -------------------------- Resolution: Fixed Fix Version/s: 2.0 Fixed in http://svn.apache.org/r1481212 > AbstractExecutor.currentPosition should be an int > ------------------------------------------------- > > Key: DBUTILS-109 > URL: https://issues.apache.org/jira/browse/DBUTILS-109 > Project: Commons DbUtils > Issue Type: Bug > Reporter: Sebb > Fix For: 2.0 > > > AbstractExecutor.currentPosition is currently an Integer. > It is only used here: > posList.add(++currentPosition); > This involves converting the Integer to an int, incrementing the int and then converting back to an Integer. > It would be rather more efficient to create the field as an int. > Alternatively, if the class is supposed to be thread-safe, maybe an AtomicInteger would be better. > Integer is not the best choice here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira