Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet - Mailing list pgsql-jdbc

From Kevin Grittner
Subject Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Date
Msg-id 4DB4B0F9020000250003CC4B@gw.wicourts.gov
Whole thread Raw
Responses Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet  (Kris Jurka <books@ejurka.com>)
List 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

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Next
From: Kris Jurka
Date:
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet