Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <books(at)ejurka(dot)com>,<dmigowski(at)ikoffice(dot)de>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Date: 2011-04-25 04:23:37
Message-ID: 4DB4B0F9020000250003CC4B@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Kris Jurka wrote:

> Integer.valueOf appeared in JDK 1.5 and we currently still support
> JDK 1.4. There's been talk of ditching 1.4 support, but that hasn't
> officially happened yet and isn't something we'd do for older
> driver releases.

Would it be practical to do it in the JDBC4 build?

On a related note, are we using the -target switch to build for the
lowest supported release (1.4 for JDBC3 and 1.6 for JDBC4)? If not,
would that be practical?

(I'm not very good at reading or writing ant....)

-Kevin

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2011-04-25 04:50:11 Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Previous Message Kris Jurka 2011-04-25 02:21:43 Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet