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

From: Lew <noone(at)lewscanon(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Date: 2011-04-25 16:44:32
Message-ID: ip48de$abj$1@news.albasani.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Robert Haas 2011-04-25 19:57:17 Re: [BUGS] [JDBC] Missing documentation for error code: 80S01
Previous Message Kevin Grittner 2011-04-25 15:46:49 Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet