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

From Lew
Subject Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Date
Msg-id ip48de$abj$1@news.albasani.net
Whole thread Raw
In response to Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-jdbc
Kevin Grittner wrote:
> Lew wrote:
>> Yeah, you have to use -bootclasspath to get the right rt.jar if
>> you use -target.
>
> I guess I didn't make my point very clearly.  I don't want to
> compile with an *earlier* target.  The *default* is to compile with
> the earlier bytecode target.  It won't actually *run* on the earlier
> JVMs because we're using the later API, so we're just hurting
> performance by *not* forcing the '-target 1.4' for -jdbc3 and
> '-target 1.6' for -jdbc4.
>
> If you don't believe me, look at this page for the bytecode level

Oh, I believe you!

--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg

pgsql-jdbc by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Next
From: "Kevin Grittner"
Date:
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet