From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, Christopher Barham <cbarham(at)digitalriver(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [JDBC] JDBC documentation - issue report |
Date: | 2014-08-20 04:27:40 |
Message-ID: | 53F423BC.3040706@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-jdbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2014-08-20 11:57:56 | Re: [DOCS] JDBC documentation - issue report |
Previous Message | Josh Berkus | 2014-08-19 18:27:47 | Re: Sample archive_command is still problematic |
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Schlichtherle | 2014-08-20 11:57:06 | Re: JDBC build broken by commit 9f9019b |
Previous Message | Craig Ringer | 2014-08-20 04:20:55 | Re: JDBC build broken by commit 9f9019b |