Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJxV5-0004M1-H3 for pgsql-docs@arkaria.postgresql.org; Wed, 20 Aug 2014 04:27:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XJxV5-0007g3-0t for pgsql-docs@arkaria.postgresql.org; Wed, 20 Aug 2014 04:27:55 +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 1XJxV4-0007fs-4J; Wed, 20 Aug 2014 04:27:54 +0000 Received: from mout.kundenserver.de ([212.227.126.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XJxV0-0002WQ-2w; Wed, 20 Aug 2014 04:27:53 +0000 Received: from ayaki.localdomain (106-68-124-192.dyn.iinet.net.au [106.68.124.192]) by mrelayeu.kundenserver.de (node=mreue007) with ESMTP (Nemesis) id 0LqJdN-1Wgmzx30Zl-00e2tY; Wed, 20 Aug 2014 06:27:46 +0200 Message-ID: <53F423BC.3040706@2ndquadrant.com> Date: Wed, 20 Aug 2014 12:27:40 +0800 From: Craig Ringer Organization: 2nd Quadrant User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Josh Berkus , Christopher Barham , "pgsql-docs@postgresql.org" , pgsql-jdbc@postgresql.org Subject: Re: [JDBC] JDBC documentation - issue report References: <9c3f9281b1e34a7485bd54144bad6068@BL2PR08MB387.namprd08.prod.outlook.com> <53F23411.303@agliodbs.com> In-Reply-To: <53F23411.303@agliodbs.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:0QUDDeud28jBET6VHxCEX/GvXOUIdyzAzySejgh/dGk 1/JAakZFQuD44/ZQM1Hg7bHhcmysUQL5BMg/PmmPL5mH56FMYf FOOqmeX3m4rXE78adfBJNzuaOrcg/aUFBuBrPXX9j9aZlDiEGI MMoR6jcMi3WSTQUYySlH/M3n9NYp5+NLXyCfDkLk8oV3f3XLM+ 8GiihjAhHLRtvFzeMQ6DI5Mb3AtvrTULFa0YBo2ONr4XD9Y9XD d7/1iXcDYO0iK6uK9ILiivmNmW4wW/rSq4L5StCdGJoXGA30XV pPjV2vNAxnSkq7xABKwEE+65A3FBrW0012kXdY0Sso2cCMMQl7 8eFcIrs3E2dtnD/3rf3iyZIZwtRaxdOvEOj7YnVLe X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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 (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs