Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XK4X2-0008LZ-OQ for pgsql-jdbc@arkaria.postgresql.org; Wed, 20 Aug 2014 11:58:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XK4X2-0004Yi-8m for pgsql-jdbc@arkaria.postgresql.org; Wed, 20 Aug 2014 11:58:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XK4X1-0004YQ-5R; Wed, 20 Aug 2014 11:58:23 +0000 Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XK4Wv-0002yb-FN; Wed, 20 Aug 2014 11:58:22 +0000 Received: by mail-wg0-f45.google.com with SMTP id x12so7608102wgg.4 for ; Wed, 20 Aug 2014 04:58:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nI3Peme2vDtcjRuC/1MEc2bXFBL2vjiVgTR5Vnif4oQ=; b=Y5GCqF6fBD8fo0hwV3/JEAF/CNhXFlUoypHoKpqdPU5WrQxaJy1h7JzlV1/OlnnXag fbzDkAKGAvuM24Ha9NsBSZs5eFHRMD9ettkmPqeKW11KH02YCMHPCOM/I/az6SjGpPff oB2CEbjwUpzrVNC9J4IiJKeIJ1A0+5pqQ6MBjW2ixICP0wedVMAZPPF0yXO3KX2SYaPf bBbHonUI0zsFRh3QuSVe4aN8UBhtJ+vkyGar780KMtZV/WhG8vroCcHiA0F1vy8BRwMm Pqe/R+/V5D7Krmh5M4CJWNelMkjOjySa6lQKkq1gGaonk+3Ajh5X4bi0i00NE63XsbEf RU0g== X-Received: by 10.195.17.170 with SMTP id gf10mr20443353wjd.111.1408535896312; Wed, 20 Aug 2014 04:58:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.204.195 with HTTP; Wed, 20 Aug 2014 04:57:56 -0700 (PDT) In-Reply-To: <53F423BC.3040706@2ndquadrant.com> References: <9c3f9281b1e34a7485bd54144bad6068@BL2PR08MB387.namprd08.prod.outlook.com> <53F23411.303@agliodbs.com> <53F423BC.3040706@2ndquadrant.com> From: Dave Cramer Date: Wed, 20 Aug 2014 07:57:56 -0400 X-Google-Sender-Auth: 21jb5-WaoUPBroQ3fsBuii6iKKs Message-ID: Subject: Re: [DOCS] JDBC documentation - issue report To: Craig Ringer Cc: Josh Berkus , Christopher Barham , "pgsql-docs@postgresql.org" , List Content-Type: multipart/alternative; boundary=089e016817dcc0ccee05010e513d X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-jdbc Precedence: bulk Sender: pgsql-jdbc-owner@postgresql.org --089e016817dcc0ccee05010e513d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ya, this really is an innocuous issue Dave Cramer dave.cramer(at)credativ(dot)ca http://www.credativ.ca On 20 August 2014 00:27, Craig Ringer wrote: > On 08/19/2014 01:12 AM, Josh Berkus wrote: > > Forwarding this to pgsql-jdbc mailing list. > > > > On 08/18/2014 06:18 AM, Christopher Barham wrote: > >> Hi, > >> > >> > >> > >> Just spotted a possible issue in the Documentation around loading the > >> JDBC driver. This page documents how: > >> http://jdbc.postgresql.org/documentation/93/load.html > >> > >> However, as of JDK6/JDBC 4.0, it should not be necessary to use the > >> > >> Class.forName("org.postgresql.Driver"); > >> > >> method to load the JDBC driver as they are automatically loaded =E2= =80=93 see > >> Javadoc here > >> > >> http://docs.oracle.com/javase/8/docs/api/java/sql/DriverManager.html > > That's valid, but minor, really; the Class.forName(...) call is harmless. > > Given how badly confused users seem to be about JDBC3 vs JDBC4 etc, I'm > reluctant to remove this until Java SE 5 is dead and gone and PgJDBC > drops JDBC4 support. Sometime around 2030 at the rate adoption of newer > releases is going. > > A note to say that explicit loading is ineffective if using a JDBC4 > driver and on Java 1.6 or newer would be reasonable. > > -- > Craig Ringer http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services > > > -- > Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc > --089e016817dcc0ccee05010e513d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ya, this really is an innocuous issue=C2=A0

Dave Cramer

dave.cramer(at)= credativ(dot)ca
htt= p://www.credativ.ca


On 20 August 2014 00:27, Craig Ringer <craig@2ndquadrant.com> wrote:
On 08/19/2014 01:12 AM, Josh Berkus wrote:
> Forwarding this to pgsql-jdbc mailing list.
>
> On 08/18/2014 06:18 AM, Christopher Barham wrote:
>> Hi,
>>
>>
>>
>> Just spotted a possible issue in the Documentation around loading = the
>> JDBC driver.=C2=A0 This page documents how:
>> http://jdbc.postgresql.org/documentation/93/load.html=
>>
>> However, as of JDK6/JDBC 4.0, it should not be necessary to use th= e
>>
>> Class.forName("org.postgresql.Driver");
>>
>> method to load the JDBC driver as they are automatically loaded=C2= =A0 =E2=80=93 see
>> Javadoc here
>>
>> http://docs.oracle.com/javase/8/docs/api/j= ava/sql/DriverManager.html

That's valid, but minor, really; the Class.forName(...) call is h= armless.

Given how badly confused users seem to be about JDBC3 vs JDBC4 etc, I'm=
reluctant to remove this until Java SE 5 is dead and gone and PgJDBC
drops JDBC4 support. Sometime around 2030 at the rate adoption of newer
releases is going.

A note to say that explicit loading is ineffective if using a JDBC4
driver and on Java 1.6 or newer would be reasonable.

--
=C2=A0Craig Ringer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0http= ://www.2ndQuadrant.com/
=C2=A0PostgreSQL Development, 24x7 Support, Training & Services


--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

--089e016817dcc0ccee05010e513d--