From: | Jorge Solórzano <jorsol(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <davecramer(at)gmail(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC 42.0.0 released |
Date: | 2017-02-20 15:00:59 |
Message-ID: | CA+cVU8PVcTsUxGTrMKxFGocCH0Gdxgp6fUm2Z_=-nq3b868syg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi Dave,
Can you please execute in your machine: gem install kramdown rouge
and rebuild the site?
And I think the actual release date is Feb 18 2017
Regards,
Jorge Solórzano
On Mon, Feb 20, 2017 at 8:40 AM, Dave Cramer <davecramer(at)gmail(dot)com> wrote:
> The JDBC group is proud to announce the release of version 42.0.0
>
> Notable changes include:
>
> *Notable changes*
>
> - Support for PostgreSQL versions below 8.2 was dropped
> - java.util.logging is now used for logging: logging documentation
> <https://jdbc.postgresql.org//documentation/head/logging.html>
> - Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc
> could use server-prepared statements for batch execution even with
> prepareThreshold=0 (see issue 742
> <https://github.com/pgjdbc/pgjdbc/issues/742>)
> - Replication protocol API was added: replication API documentation
> <https://jdbc.postgresql.org//documentation/head/replication.html>, GitHub
> PR 550 <https://github.com/pgjdbc/pgjdbc/pull/550>
> - Version bumped to 42.0.0 to avoid version clash with PostgreSQL
> version
> - Error position is displayed when SQL has unterminated literals,
> comments, etc (see issue 688
> <https://github.com/pgjdbc/pgjdbc/issues/688>)
>
> You may have noticed the change in the versioning of the driver, you can read
> the FAQ <https://jdbc.postgresql.org/documentation/faq.html#versioning> for
> more information.
>
> Regards,
> Dave Cramer
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2017-02-20 15:04:24 | Re: JDBC 42.0.0 released |
Previous Message | Dave Cramer | 2017-02-20 14:40:12 | JDBC 42.0.0 released |