Обсуждение: [JDBC] JDBC 42.0.0 released

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
• Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
• Replication protocol API was added: replication API documentation, GitHub PR 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)

You may have noticed the change in the versioning of the driver, you can read the FAQ for more information.

Regards,

Dave Cramer

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
• Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
• Replication protocol API was added: replication API documentation, GitHub PR 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)

You may have noticed the change in the versioning of the driver, you can read the FAQ for more information.

Regards,

Dave Cramer

Dave Cramer schrieb am 20.02.2017 um 15:40:
>   * Version bumped to 42.0.0 to avoid version clash with PostgreSQL version

Thanks for all the work!

I seem to recall that you not only switched the version number, but also switched to semantic versioning with that release?

If that is true, I think a short note for that would also be helpful to understand the sudden jump in the version number.

www.postgresintl.com

Dave Cramer schrieb am 20.02.2017 um 15:40:
>   * Version bumped to 42.0.0 to avoid version clash with PostgreSQL version

Thanks for all the work!

I seem to recall that you not only switched the version number, but also switched to semantic versioning with that release?

If that is true, I think a short note for that would also be helpful to understand the sudden jump in the version number.

www.postgresintl.com

Hi Jorge,

I do not build this on my machine. I build it on the target machine. As it is I am being forced to build it on another machine now because Jekyll 3.x is required. 

I think it would be better if we avoid any special packages, and also make it jekyll 2.x compatible. I am unable to run any command which requires root on the target machine.

As for when it is released,

​​

this is moot. The official release was today.

Thanks,

Hi Jorge,

I do not build this on my machine. I build it on the target machine. As it is I am being forced to build it on another machine now because Jekyll 3.x is required. 

I think it would be better if we avoid any special packages, and also make it jekyll 2.x compatible. I am unable to run any command which requires root on the target machine.

As for when it is released,

​​

this is moot. The official release was today.

Thanks,

Jorge,

* Jorge Solórzano (jorsol@gmail.com) wrote:
> On Mon, Feb 20, 2017 at 9:11 AM, Dave Cramer <davecramer@gmail.com> wrote:
> > I do not build this on my machine. I build it on the target machine. As it
> > is I am being forced to build it on another machine now because Jekyll 3.x
> > is required.
> >
> > I think it would be better if we avoid any special packages, and also make
> > it jekyll 2.x compatible. I am unable to run any command which requires
> > root on the target machine.
> >
>
> Can't be requested to install jekyll 3.x on the target machine? those
> packages are part of jekyll 3.x. If not I will try to make it jekyll 2.x
> compatible.

jekyll 3.x is not available on

​​

Debian/stable (jessie) in a way which is
packaged and maintainable through our infrastructure.  Making it jekyll
2.x compatible would be very helpful.

The next version of Debian includes jekyll 3.x and will be released
later this year.  We will likely upgrade to it shortly after it's
released (think fall of 2017).

Thanks!

Stephen

Jorge,

* Jorge Solórzano (jorsol@gmail.com) wrote:
> On Mon, Feb 20, 2017 at 9:11 AM, Dave Cramer <davecramer@gmail.com> wrote:
> > I do not build this on my machine. I build it on the target machine. As it
> > is I am being forced to build it on another machine now because Jekyll 3.x
> > is required.
> >
> > I think it would be better if we avoid any special packages, and also make
> > it jekyll 2.x compatible. I am unable to run any command which requires
> > root on the target machine.
> >
>
> Can't be requested to install jekyll 3.x on the target machine? those
> packages are part of jekyll 3.x. If not I will try to make it jekyll 2.x
> compatible.

jekyll 3.x is not available on

​​

Debian/stable (jessie) in a way which is
packaged and maintainable through our infrastructure.  Making it jekyll
2.x compatible would be very helpful.

The next version of Debian includes jekyll 3.x and will be released
later this year.  We will likely upgrade to it shortly after it's
released (think fall of 2017).

Thanks!

Stephen