public inbox for [email protected]  

help / color / mirror / Atom feed

From: Craig Ringer <[email protected]>
To: Josh Berkus <[email protected]>
To: Christopher Barham <[email protected]>
To: [email protected] <[email protected]>
To: [email protected]
Subject: Re: [JDBC] JDBC documentation - issue report
Date: Wed, 20 Aug 2014 12:27:40 +0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <9c3f9281b1e34a7485bd54144bad6068@BL2PR08MB387.namprd08.prod.outlook.com>
	<WM!cfee82d1a9b0818a3156beb7adee321c0a3e1c2f1f29446c7653625868468ee1b7f12e58e79151c4895950669c495010!@asav-2.01.com>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

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  – 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-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [JDBC] JDBC documentation - issue report
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox